From: | "Jim Buttafuoco" <jim(at)contactbda(dot)com> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | xlog flush request not satisfied after server reboot |
Date: | 2006-12-15 16:02:38 |
Message-ID: | 200612151602.kBFG2eGc032201@amanda.contactbda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hackers,
I had a server reboot for an unknown reason, after the server restarted one
of the disks was not mounted before Postgresql tried to start. The startup
failed (see log below), after I mounted the disks and tried to start
Postgresql again there was a HINT about corrupted data and a WARNING about
invalid page headers. The warning didn't tell me which database had the
invalid page, so I decided to vacuum full all of the databases to see if I
received an error which I did (see below). The database with the error is
the largest ~300GB, I do have a backup if necessary, is there away to
recover without doing a restore?
Thanks for your help
Jim
startup with tablespace not mounted
----------------------------------------------------------------------------
-----------------------------
LOG: database system was interrupted at 2006-12-14 19:51:26 EST
LOG: checkpoint record is at 1F1/52C8A704
LOG: redo record is at 1F1/5291F0A0; undo record is at 0/0; shutdown FALSE
LOG: next transaction ID: 13019683; next OID: 4167831
LOG: next MultiXactId: 1; next MultiXactOffset: 0
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 1F1/5291F0A0
PANIC: could not create directory "pg_tblspc/3717272": File exists
LOG: startup process (PID 4987) was terminated by signal 6
LOG: aborting startup due to startup process failure
LOG: logger shutting down
startup after tablespace was mounted
----------------------------------------------------------------------------
-----------------------------
LOG: database system was interrupted while in recovery at 2006-12-15
08:04:48 E
ST
HINT: This probably means that some data is corrupted and you will have to
use
the last backup for recovery.
LOG: checkpoint record is at 1F1/52C8A704
LOG: redo record is at 1F1/5291F0A0; undo record is at 0/0; shutdown FALSE
LOG: next transaction ID: 13019683; next OID: 4167831
LOG: next MultiXactId: 1; next MultiXactOffset: 0
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 1F1/5291F0A0
WARNING: invalid page header in block 6196744 of relation "4158697";
zeroing ou
t page
LOG: connection received: host=s20a.contactbda.com port=1667
FATAL: the database system is starting up
WARNING: invalid page header in block 6196934 of relation "4158697";
zeroing ou
t page
LOG: record with zero length at 1F1/572B792C
LOG: redo done at 1F1/572B5BD0
LOG: database system is ready
Error message from vacuum
----------------------------------------------------------------------------
------------------------
ERROR: xlog flush request 1F6/3A0F605C is not satisfied --- flushed only to
1F1
/57CD76FC
CONTEXT: writing block 3387032 of relation 3717272/4158444/4158627
_____________________________________________
Jim Buttafuoco
Contact Telecom LLC
Office: 603-647-7170
Fax: 603-606-4243
Cell: 603-490-3409
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2006-12-15 16:07:07 | Re: invalid input syntax for type timestamp. |
Previous Message | Christopher Browne | 2006-12-15 16:01:55 | Re: invalid input syntax for type timestamp. |