By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,834 Members | 2,265 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,834 IT Pros & Developers. It's quick & easy.

Database corupption on pg 7.3.3

P: n/a
Hi,
I have had two times problem with pg database corruption.
My system:

Dual athlon 2.4
1 GB RAM,
linux red hat 7.3
reiserFS

Also on the system I have cron that every 3 h. make dump and every 24 h.
make vacuum full analyze.

After working some days pg crashes and I was not able to restore it.

I found tis messages into the log:
Lock file "/mnt/diske/skladdb/postmaster.pid" already exists.
Is another postmaster (pid 1208) running in "/mnt/diske/skladdb"?
LOG: database system was interrupted at 2003-08-22 20:10:51 EEST
LOG: checkpoint record is at 0/1829A1E4
LOG: redo record is at 0/1829A1E4; undo record is at 0/0; shutdown
FALSE
LOG: next transaction id: 45726; next oid: 13875914
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 0/1829A224
PANIC: Invalid page header in block 4 of 16645
LOG: startup process (pid 1212) was terminated by signal 6
LOG: aborting startup due to startup process failure
LOG: database system was interrupted being in recovery at 2003-08-25
09:03:14 EEST
This probably means that some data blocks are corrupted
and you will have to use the last backup for recovery.
LOG: checkpoint record is at 0/1829A1E4
LOG: redo record is at 0/1829A1E4; undo record is at 0/0; shutdown
FALSE
LOG: next transaction id: 45726; next oid: 13875914
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 0/1829A224
PANIC: Invalid page header in block 4 of 16645
LOG: startup process (pid 1211) was terminated by signal 6
LOG: aborting startup due to startup process failure
LOG: database system was interrupted being in recovery at 2003-08-25
09:10:29 EEST
This probably means that some data blocks are corrupted
and you will have to use the last backup for recovery.
LOG: checkpoint record is at 0/1829A1E4
LOG: redo record is at 0/1829A1E4; undo record is at 0/0; shutdown
FALSE
LOG: next transaction id: 45726; next oid: 13875914
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 0/1829A224
PANIC: Invalid page header in block 4 of 16645
LOG: startup process (pid 1211) was terminated by signal 6
LOG: aborting startup due to startup process failure

Pls, help me to solve this problem.

regards,
ivan.
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 11 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

7.3.4 fixes a problem with recovery failure after crash. You should
definitely upgrade.

On Sat, Aug 30, 2003 at 10:44:07AM +0200, pginfo wrote:
After working some days pg crashes and I was not able to restore it.

I found tis messages into the log:
Lock file "/mnt/diske/skladdb/postmaster.pid" already exists.
Is another postmaster (pid 1208) running in "/mnt/diske/skladdb"?
LOG: database system was interrupted at 2003-08-22 20:10:51 EEST
LOG: checkpoint record is at 0/1829A1E4
LOG: redo record is at 0/1829A1E4; undo record is at 0/0; shutdown
FALSE
LOG: next transaction id: 45726; next oid: 13875914
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 0/1829A224
PANIC: Invalid page header in block 4 of 16645


--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Puedes vivir solo una vez, pero si lo haces bien, una vez es suficiente"

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)

Nov 11 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.