From: Benjamin Krajmalnik <kraj@servoyant.com>
To: Craig Ringer <craig@2ndQuadrant.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Possible database corruption
Date: Mon, 7 Jan 2013 19:30:57 -0700
Message-ID: <F4E6A2751A2823418A21D4A160B6898892B7CB@fletch.stackdump.local> (raw)
In-Reply-To: <50EB833C.4060206@2ndQuadrant.com>
References: <F4E6A2751A2823418A21D4A160B6898892B7BB@fletch.stackdump.local>
<50EB833C.4060206@2ndQuadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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:craig@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
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: kraj@servoyant.com, craig@2ndQuadrant.com
Subject: Re: Possible database corruption
In-Reply-To: <F4E6A2751A2823418A21D4A160B6898892B7CB@fletch.stackdump.local>
References: <F4E6A2751A2823418A21D4A160B6898892B7BB@fletch.stackdump.local> <50EB833C.4060206@2ndQuadrant.com> <F4E6A2751A2823418A21D4A160B6898892B7CB@fletch.stackdump.local>
* 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