From: Craig Ringer <ringerc@ringerc.id.au>
To: Walter Hurry <walterhurry@lavabit.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: bad block problem
Date: Thu, 08 Dec 2011 09:02:15 +0800
Message-ID: <4EE00C97.3080905@ringerc.id.au> (raw)
In-Reply-To: <jbovsn$kkf$1@dough.gmane.org>
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>
<jbovsn$kkf$1@dough.gmane.org>
On 12/08/2011 08:20 AM, Walter Hurry wrote:
> 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.
Unless you're using synchronous replication to clone *every* transaction
on commit to a spare machine, you'll still lose transactions on a
failure no matter how good your backups are.
Even if the OP was doing nightly dumps, they'd be entirely justified in
wanting to try to get a more recent dump on failure.
If they're not backing up at all, yes, that was dumb, but they know that
now. Asking for help isn't unreasonable, and this isn't a stupid "just
google it" question. They've made an effort, posted useful info and log
output, etc. Please don't be too hard on them.
--
Craig Ringer
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: ringerc@ringerc.id.au, walterhurry@lavabit.com
Subject: Re: bad block problem
In-Reply-To: <4EE00C97.3080905@ringerc.id.au>
* 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