Thanks for the reply - I posted an update that I had resolved the issue. When the partition with the WAL files filled up due to the missing fsm file (I wonder what caused that), the db panicked.
After moving all 43GB of WAL files to a different partition, database came into recovery mode, and after about half an hour of processing the WAL files the server came back online. The only thing that is still pending is for the system to clean out all of the now unused wal files. Once this is done, I will move back the WAL files to their own spindle. Since the database would not restart until the WAL files were moved I feared data corruption - which thankfully did not occur. DB was Postgres 9.0.4 running on FreeBSD 8.1/amd64. Subsystem is dual RAID-1 SAS, OS/WAL on one set of spindles, data on the other. From: Craig Ringer [mailto:cr...@2ndquadrant.com] Sent: Monday, January 07, 2013 7:24 PM To: Benjamin Krajmalnik Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Possible database corruption On 01/08/2013 05:22 AM, Benjamin Krajmalnik wrote: I have a situation where pg_xlog started growing until it filled up the disk drive. This should not ever cause corruption. If it has, there's a bug at work. A crash is reasonable (albeit undesirable; it'd be better to just report errors on connections) - but database corruption is not. Before doing ANYTHING else, read http://wiki.postgresql.org/wiki/Corruption and act on it. How big is the DB? What file system is it on? PostgreSQL 9.0.[what?] ? Host OS? Disk subsystem? -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
