From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ken Caruso <ken@ipl31.net>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: 9.0.4 Data corruption issue
Date: Sat, 16 Jul 2011 17:30:30 -0400
Message-ID: <23808.1310851830@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMg8r_rbdiQDe+Vr3M0PdxSKHmmxM42C1gWAwx6uObPoXEJiJQ@mail.gmail.com>
References: <CAMg8r_rzsTn+pR0+A0xCXS73o5QsTdgsisW9AHG6jEm87r1FCQ@mail.gmail.com>
<27386.1310831992@sss.pgh.pa.us>
<CAMg8r_rbdiQDe+Vr3M0PdxSKHmmxM42C1gWAwx6uObPoXEJiJQ@mail.gmail.com>
Ken Caruso <ken@ipl31.net> writes:
> Sorry, the actual error reported by CLUSTER is:
> gpup=> cluster verbose tablename;
> INFO: clustering "dbname.tablename"
> WARNING: could not write block 12125253 of base/2651908/652397108
> DETAIL: Multiple failures --- write error might be permanent.
> ERROR: could not open file "base/2651908/652397108.1" (target block
> 12125253): No such file or directory
> CONTEXT: writing block 12125253 of relation base/2651908/652397108
Hmm ... it looks like you've got a dirty buffer in shared memory that
corresponds to a block that no longer exists on disk; in fact, the whole
table segment it belonged to is gone. Or maybe the block or file number
in the shared buffer header is corrupted somehow.
I imagine you're seeing errors like this during each checkpoint attempt?
I can't think of any very good way to clean that up. What I'd try here
is a forced database shutdown (immediate-mode stop) and see if it starts
up cleanly. It might be that whatever caused this has also corrupted
the back WAL and so WAL replay will result in the same or similar error.
In that case you'll be forced to do a pg_resetxlog to get the DB to come
up again. If so, a dump and reload and some manual consistency checking
would be indicated :-(
regards, tom lane
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: tgl@sss.pgh.pa.us, ken@ipl31.net
Subject: Re: 9.0.4 Data corruption issue
In-Reply-To: <23808.1310851830@sss.pgh.pa.us>
* 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