Bad pg_xlog with no redo - Mailing list pgsql-general

From Pailloncy Jean-Gerard
Subject Bad pg_xlog with no redo
Date
Msg-id 7996ABD5-1197-4101-8613-A8113D49053D@rilk.com
Whole thread Raw
Responses Re: Bad pg_xlog with no redo  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi,

I have a drive with a bad zone inside the file pgsql/pg_xlog/
0000005D000000A1.
After trying to start few time pg, I get the follwing message in log:

2005-06-14 23:35:44 LOG:  database system shutdown was interrupted at
2005-06-14 12:20:42 CEST
2005-06-14 23:35:44 LOG:  checkpoint record is at 5D/A1E1BF94
2005-06-14 23:35:44 LOG:  redo record is at 5D/A1E1BF94; undo record
is at 0/0; shutdown TRUE
2005-06-14 23:35:44 LOG:  next transaction ID: 180308042; next OID:
29965668
2005-06-14 23:35:44 LOG:  database system was not properly shut down;
automatic recovery in progress
2005-06-14 23:37:40 FATAL:  the database system is starting up
2005-06-14 23:38:38 LOG:  could not read from log file 93, segment
161, offset 14794752: Input/output error
2005-06-14 23:38:38 LOG:  redo is not required
2005-06-14 23:40:05 FATAL:  the database system is starting up
2005-06-14 23:41:32 FATAL:  the database system is starting up
2005-06-14 23:42:02 FATAL:  the database system is starting up
2005-06-14 23:42:02 FATAL:  the database system is starting up
2005-06-14 23:42:59 FATAL:  the database system is starting up
2005-06-14 23:43:28 FATAL:  the database system is starting up
2005-06-14 23:44:26 PANIC:  could not write to log file 93, segment
161 at offset 14794752: Input/output error
2005-06-14 23:44:29 LOG:  startup process (PID 14991) was terminated
by signal 6
2005-06-14 23:44:29 LOG:  aborting startup due to startup process
failure

2005-06-14 23:47:07 LOG:  database system shutdown was interrupted at
2005-06-14 23:38:38 CEST
2005-06-14 23:47:07 LOG:  checkpoint record is at 5D/A1E1BF94
2005-06-14 23:47:07 LOG:  redo record is at 5D/A1E1BF94; undo record
is at 0/0; shutdown TRUE
2005-06-14 23:47:07 LOG:  next transaction ID: 180308042; next OID:
29965668
2005-06-14 23:47:07 LOG:  database system was not properly shut down;
automatic recovery in progress
2005-06-14 23:52:26 FATAL:  the database system is starting up
2005-06-14 23:52:55 LOG:  could not read from log file 93, segment
161, offset 14794752: Input/output error
2005-06-14 23:52:55 LOG:  redo is not required
2005-06-14 23:58:43 PANIC:  could not write to log file 93, segment
161 at offset 14794752: Input/output error
2005-06-14 23:58:46 LOG:  startup process (PID 1394) was terminated
by signal 6
2005-06-14 23:58:46 LOG:  aborting startup due to startup process
failure

How may I zap the bad pgxlog file ?

Cordialement,
Jean-Gérard Pailloncy


pgsql-general by date:

Previous
From: Zlatko Matić
Date:
Subject: users/users groups management from MS Access front-end
Next
From: John DeSoi
Date:
Subject: Re: user groups