Hi,
My production is running PostgreSQL v8.2.3 on CentOS release 5.2 (Final).
As part of our routine, we just wanted to make sure and practice once in a
while, whether PITR recovery process is performed without fail. When I
started the recovery process, after sometime, I see the following error in
the serverlog. This error was thrown after processing WAL archives for
almost 2 and half hour. I couldn't able to understand what is wrong by
reading this error statements, since it is cryptic technically. Can experts
help me in this regard? How do I proceed further from here?
I do have enough space in both my data/ and /mnt/pitr/walarchive/
directories. I don't think this is because of scarcity in disk space.
My base backup date: Aug03, 2009
recovery.conf
===========
restore_command='cp /mnt/pitr/walarchive/%f "%p"'
recovery_target_time='2010-06-08 09:10'
recovery_target_inclusive='true'
ERROR
======
[]:2010-06-09 04:43:27 EDTLOG: restored log file "00000001000000130000003D"
from archive
[]:2010-06-09 04:43:29 EDTLOG: restored log file "00000001000000130000003E"
from archive
[]:2010-06-09 04:43:30 EDTLOG: restored log file "00000001000000130000003F"
from archive
[]:2010-06-09 04:44:59 EDTLOG: could not fsync segment 0 of relation
1663/169462/252056: No such file or directory
[]:2010-06-09 04:44:59 EDTCONTEXT: xlog redo checkpoint: redo 13/3FE33EB0;
undo 0/0; tli 1; xid 0/331456443; oid 256783; multi 337; offset 676; online
[]:2010-06-09 04:44:59 EDTFATAL: storage sync failed on magnetic disk: No
such file or directory
[]:2010-06-09 04:44:59 EDTCONTEXT: xlog redo checkpoint: redo 13/3FE33EB0;
undo 0/0; tli 1; xid 0/331456443; oid 256783; multi 337; offset 676; online
[]:2010-06-09 04:44:59 EDTLOG: startup process (PID 22855) exited with exit
code 1
[]:2010-06-09 04:44:59 EDTLOG: aborting startup due to startup process
failure
[]:2010-06-09 04:44:59 EDTLOG: logger shutting down
Regards,
Gnanam
