Re: BUG #4626: postgresql recovery problem - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #4626: postgresql recovery problem
Date
Msg-id 20090123182256.GN4047@alvh.no-ip.org
Whole thread Raw
In response to BUG #4626: postgresql recovery problem  ("Steven Mezzadri" <smezzadr@livonia.k12.mi.us>)
List pgsql-bugs
Steven Mezzadri wrote:

> The database for our moodle web site (uses PHP/postgres 8.1.11/Linux) has
> stopped working.  The server froze yesterday and we had to cycle power to
> resolve the issue.  Now the postgresql service will not start.  I tried a
> backup from last week and get the same result.  I have no other backups or
> dumps.  I have tried running fsck.  The disks are in a RAID-1 array and
> neither disk has failed.  I did not run out of RAM or disk space.

> -bash-3.2$ tail postgresql-Fri.log
> ERROR:  could not open relation 1663/16384/435720012: No such file or
> directory
> CONTEXT:  writing block 1 of relation 1663/16384/435720012
> WARNING:  could not write block 1 of 1663/16384/435720012
> DETAIL:  Multiple failures --- write error may be permanent.

Ugh.

What filesystem is this using?  Sounds like it lost a file.  Maybe it
ended up in lost+found or something?

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: "Steven Mezzadri"
Date:
Subject: BUG #4626: postgresql recovery problem
Next
From: Francesco Pari
Date:
Subject: Selecting from a Subquery Fails