8.3.5 broken after power fail

From: Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at>
To: pgsql-admin(at)postgresql(dot)org
Subject: 8.3.5 broken after power fail
Date: 2009-02-17 08:54:52
Message-ID: 200902170954.52983@zmi.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Now I'm sure that the following configuration can destroy your database:

* Linux host with XEN, XFS filesystem with "nobarrier", RAID controller
with battery backed cache.
* XEN vm with XFS filesystem with "nobarrier" with postgresql
* your daughter with 3.5 years switching off the power supply of the
server
I guess one shouldn't use "nobarrier" on a XEN XFS domU machine.

Now, can somebody help me fixing this error? I did "vacuum analyze
verbose" and it stopped here:

INFO: vacuuming "pg_toast.pg_toast_1281127"
ERROR: could not access status of transaction 2299723776
DETAIL: Could not open file "pg_clog/0891": No such file or directory.

What can I do?

mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Achilleas Mantzios 2009-02-17 09:12:31 Re: 8.3.5 broken after power fail
Previous Message Rajesh Kumar Mallah 2009-02-16 20:44:05 tsearch2 migration 8.2 --> 8.3