From: Stefan Holzheu <stefan.holzheu@bitoek.uni-bayreuth.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: ADMIN <pgsql-admin@postgresql.org>
Subject: Re: Servercrash
Date: Thu, 20 May 2004 12:21:38 +0200
Message-ID: <40AC86B2.8040301@bitoek.uni-bayreuth.de> (raw)
In-Reply-To: <22443.1085010261@sss.pgh.pa.us>
References: <40AB87CC.8020500@bitoek.uni-bayreuth.de>
<22443.1085010261@sss.pgh.pa.us>
>
>>yesterday our database-server crashed (raid-error). After reparing the
>>filesystem (ext2) we have a problem with our lagest table in the database.
>
>
>>vaccuum aborts with the following meassage (sorry it is in German):
>
>
>>DEBUG: vacuume »messungen.massendaten«
>>HINWEIS: Relation »massendaten« TID 211540/73:
>>DeleteTransactionInProgress 16785658 --- kann Relation nicht verkleinern
>>(cannot shrink relation)
>>DEBUG: AbortCurrentTransaction
>>FEHLER: ungültiger Seitenkopf in Block 354500 von Relation
>>»massendaten« (unvalid pagehead in block ...)
>
>
>>All other operations using ctid 211540/73 give:
>
>
>>FEHLER: konnte auf den Status von Transaktion 16785658 nicht zugreifen
>>(could not get status of transaction ...)
>>DETAIL: konnte Datei »/var/lib/pgsql/data/pg_clog/0010« nicht öffnen:
>>Datei oder Verzeichnis nicht gefunden
>
>
>>Is there a way to repair the database?
>
>
> You have at least two corrupted pages in that table: page 354500 has a
> header problem, and in page 211540 there's a bogus transaction ID in a
> tuple header. These are the *minimum* descriptions of the data lossage,
> it's entirely likely that large parts of the pages involved are junk.
>
> I would suggest proceeding by examining those pages with pg_filedump or
> another tool. If you can make some sense of the damage it might be
> possible to do a selective repair. If not, your best bet is to just
> zero out the damaged pages --- this will lose the rows that are on those
> pages, but at least you can get the rest of the table operational again.
>
> You can find more about this by looking in the mail list archives.
> Threads mentioning pg_filedump would be good places to start.
>
> regards, tom lane
>
>
We set zero_damaged_pages to on and get rid of page 354500. But the
error in page 211540 remains :-(...
Any idea?
Stefan
--
-----------------------------
Dr. Stefan Holzheu
Tel.: 0921/55-5720
Fax.: 0921/55-5799
BITOeK Wiss. Sekretariat
Universitaet Bayreuth
D-95440 Bayreuth
-----------------------------
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: stefan.holzheu@bitoek.uni-bayreuth.de, tgl@sss.pgh.pa.us
Subject: Re: Servercrash
In-Reply-To: <40AC86B2.8040301@bitoek.uni-bayreuth.de>
References: <40AB87CC.8020500@bitoek.uni-bayreuth.de> <22443.1085010261@sss.pgh.pa.us> <40AC86B2.8040301@bitoek.uni-bayreuth.de>
* 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