Re: (Again) Datacorruption using 7.4.2 on XFS/raid1 - Mailing list pgsql-general

From Ian Barwick
Subject Re: (Again) Datacorruption using 7.4.2 on XFS/raid1
Date
Msg-id 1d581afe040712133843b5d325@mail.gmail.com
Whole thread Raw
In response to (Again) Datacorruption using 7.4.2 on XFS/raid1  ("Florian G. Pflug" <fgp@phlo.org>)
List pgsql-general
On Mon, 12 Jul 2004 20:31:15 +0200, Florian G. Pflug <fgp@phlo.org> wrote:
> Hi
>
> We have again experienced data-corruption using 7.4.2 on an XFS Filesystem
> on top of a software-raid (md) raid-1.
>
> After a server crash last night (It was a rather strange crash - The machine
> was still pingable, but no login was possible, and postgres and apache
> didn't respond to requests any more) we hard-reset the machine. It came up
> again nicely, but a few hours later the following errors occured when trying
> to access certain tabled. (Those tables are updated heavily - each day about
> 2 million tuples are inserted, and the old versions of those tuples
> deleted).
>
> ERROR:  could not access status of transaction 34048
> DETAIL:  could not open file "/var/lib/postgres/data/pg_clog/0000": No such
> file or directory

You don't say what kind of disks you are using. Sounds very much like
hardware problems though.

I had a PostgreSQL installation on a pair of IDE disks with software
RAID1 / Ext3 die very nastily with similar error messages. Turned out
that one of the disks was very defective and the RAID wasn't handling
it.

On the other hand - after copying the files from the good disk,
PostgreSQL started with barely a complaint and I couldn't detect any
corruption.

Ian Barwick

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Latitude/Longitude data types and functions
Next
From: Peter Eisentraut
Date:
Subject: Re: make install (in contrib) and PGDATA