Обсуждение: invalid primary checkpoint record
dear all we have the following issues and cannot start the postgresql server: postgresql 8.0.5 redhat EL WS4 U3 the computer was shutdown properly. then the user restarted the computer, in the middle of rebooting, he switched off the power button on the wall. after that we cannot start the database server any more. the following is the log. please help. thanks cheng LOG: database system shutdown was interrupted at 2006-06-26 10:33:11 BST LOG: could not open file "/var/lib/pgsql/data/pg_xlog/000000010000000000000000" (log file 0, segment 0): No such file or directory LOG: invalid primary checkpoint record LOG: could not open file "/var/lib/pgsql/data/pg_xlog/000000010000000000000000" (log file 0, segment 0): No such file or directory LOG: invalid secondary checkpoint record PANIC: could not locate a valid checkpoint record LOG: startup process (PID 29959) was terminated by signal 6 LOG: aborting startup due to startup process failure LOG: logger shutting down LOG: database system shutdown was interrupted at 2006-06-26 10:33:11 BST LOG: could not open file "/var/lib/pgsql/data/pg_xlog/000000010000000000000000" (log file 0, segment 0): No such file or directory LOG: invalid primary checkpoint record LOG: could not open file "/var/lib/pgsql/data/pg_xlog/000000010000000000000000" (log file 0, segment 0): No such file or directory LOG: invalid secondary checkpoint record PANIC: could not locate a valid checkpoint record LOG: startup process (PID 30015) was terminated by signal 6 LOG: aborting startup due to startup process failure LOG: logger shutting down Euro-China Medlink ltd http://www.euro-china.co.uk ___________________________________________________________ Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
zhicheng wang <wang_zc@yahoo.co.uk> writes: > the computer was shutdown properly. then the user > restarted the computer, in the middle of rebooting, he > switched off the power button on the wall. after that > we cannot start the database server any more. the > following is the log. please help. You can probably get out of this with pg_resetxlog, but after that you need to take a hard look at that machine's disk drive setup. It's evidently lying about write-complete (ie, not doing writes in the commanded order), else you could not have got into this state. regards, tom lane