| From: | "Benjamin Krajmalnik" <kraj(at)servoyant(dot)com> |
|---|---|
| To: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Possible database corruption - urgent |
| Date: | 2013-01-07 21:22:25 |
| Message-ID: | F4E6A2751A2823418A21D4A160B6898892B7BB@fletch.stackdump.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Krajmalnik | 2013-01-07 21:31:29 | Re: Possible database corruption - urgent |
| Previous Message | Armin Resch | 2013-01-07 21:19:58 | Re: Using pre-configured vs building Postgres |