Discussion:
pg_clog after crash
(too old to reply)
Andreas Schmitz
2004-06-11 11:46:36 UTC
Permalink
Hello *,

after a harddisk filling up to a 100% the database crashed. This is the output
I get when I try to start the DB again. Is there any chance to get it back
running without using a dump ?


regards,

-Andreas



2004-06-11 13:38:23 [22379] LOG: database system was interrupted while in
recovery at 2004-06-11 13:32:44 CEST
HINT: This probably means that some data is corrupted and you will have to
use the last backup for recovery.
2004-06-11 13:38:23 [22379] LOG: checkpoint record is at 25/FB90EFA4
2004-06-11 13:38:23 [22379] LOG: redo record is at 25/FB90ED88; undo record
is at 0/0; shutdown FALSE
2004-06-11 13:38:23 [22379] LOG: next transaction ID: 10185227; next OID:
17088234
2004-06-11 13:38:23 [22379] LOG: database system was not properly shut down;
automatic recovery in progress
2004-06-11 13:38:23 [22379] LOG: redo starts at 25/FB90ED88
2004-06-11 13:38:24 [22379] PANIC: could not access status of transaction
10256385
DETAIL: could not read from file "/var/data/pgsql/data/dbs_1/pg_clog/0009" at
offset 204800: Success
2004-06-11 13:38:24 [22373] LOG: startup process (PID 22379) was terminated
by signal 6
2004-06-11 13:38:24 [22373] LOG: aborting startup due to startup process
failure



---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ***@postgresql.org so that your
message can get through to the mailing list cleanly
Tom Lane
2004-06-11 18:01:07 UTC
Permalink
Post by Andreas Schmitz
after a harddisk filling up to a 100% the database crashed. This is
the output I get when I try to start the DB again. Is there any chance
to get it back running without using a dump ?
What PG version is this?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ***@postgresql.org
Andreas Schmitz
2004-06-14 08:10:13 UTC
Permalink
Hi Tom,

PostgreSQL 7.4.1 is used in this case. I was able to fix the clog by

dd if=/dev/zero bs=8k count=1 >><CLOG_FILE


regards,

-andreas
Post by Tom Lane
Post by Andreas Schmitz
after a harddisk filling up to a 100% the database crashed. This is
the output I get when I try to start the DB again. Is there any chance
to get it back running without using a dump ?
What PG version is this?
regards, tom lane
---------------------------(end of broadcast)---------------------------
--
Andreas Schmitz - Phone +49 201 8501 318
Cityweb-Technik-Service-Gesellschaft mbH
Friedrichstr. 12 - Fax +49 201 8501 104
45128 Essen - email ***@cityweb.de


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html
Tom Lane
2004-06-14 12:25:04 UTC
Permalink
Post by Andreas Schmitz
Post by Tom Lane
What PG version is this?
PostgreSQL 7.4.1 is used in this case.
Now that I look at it, your report matches Chris K-L's trouble
http://archives.postgresql.org/pgsql-hackers/2004-01/msg00530.php
which is fixed in 7.4.2.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Loading...