From: Walter Hurry <walterhurry@lavabit.com>
To: pgsql-admin@postgresql.org
Subject: Re: bad block problem
Date: Thu, 8 Dec 2011 00:20:40 +0000 (UTC)
Message-ID: <jbovsn$kkf$1@dough.gmane.org> (raw)
References: <1OQDq.131420$034.90105@en-nntp-06.dc1.easynews.com>
<jboo6j$2fo$1@dough.gmane.org>
<OERDq.160636$Hr1.91214@en-nntp-03.dc1.easynews.com>
On Wed, 07 Dec 2011 22:20:30 +0000, jkells wrote:
> I am relying on identifying and correcting a bad block.
Well, good luck with that. Most of the time you can't. Just check your
disk, replace it if necessary, restore from your backup and roll forward.
Oh, you can't do that, since you didn't bother to back up. Never mind.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: walterhurry@lavabit.com
Subject: Re: bad block problem
In-Reply-To: <jbovsn$kkf$1@dough.gmane.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox