From: Benjamin Krajmalnik <kraj@servoyant.com>
To: pgsql-admin@postgresql.org
Subject: Possible database corruption - urgent
Date: Mon, 7 Jan 2013 14:22:25 -0700
Message-ID: <F4E6A2751A2823418A21D4A160B6898892B7BB@fletch.stackdump.local> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
I have a situation where pg_xlog started growing until it filled up the
disk drive.
I got alerted to the error and started investigating.
Checked the logs and I am seeing the following entry repeatedly:
2013-01-07 01:49:12 GMT ERROR: could not open file
"base/16748/181979366_fsm": No such file or directory
2013-01-07 01:49:12 GMT CONTEXT: writing block 1 of relation
base/16748/181979366_fsm
2013-01-07 01:49:12 GMT WARNING: could not write block 1 of
base/16748/181979366_fsm
I checked the actual file system, and that file is indeed missing.
181979366 exists.
Is there a way to get the system back up and running?
I stopped the postmaster and am moving the pg_xlog directory to a
partition which has room left in it, but I need to resolve this missing
file problem
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: kraj@servoyant.com
Subject: Re: Possible database corruption - urgent
In-Reply-To: <F4E6A2751A2823418A21D4A160B6898892B7BB@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