Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 571AA632346 for ; Wed, 9 Jun 2010 06:11:28 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 59100-08 for ; Wed, 9 Jun 2010 09:11:20 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from rs47.luxsci.com (rs47.luxsci.com [65.61.166.88]) by mail.postgresql.org (Postfix) with ESMTP id 29AA66321D2 for ; Wed, 9 Jun 2010 06:11:20 -0300 (ADT) Received: from gnanam (ABTS-TN-Static-186.58.165.122.airtelbroadband.in [122.165.58.186] (may be forged)) (authenticated bits=0) by rs47.luxsci.com (8.13.1/8.13.7) with ESMTP id o599BGM7023656; Wed, 9 Jun 2010 04:11:18 -0500 Reply-To: From: "Gnanakumar" To: Subject: Fatal Error during PITR Recovery Date: Wed, 9 Jun 2010 14:41:14 +0530 Organization: Zoniac Software Private Limited Message-ID: <01e701cb07b3$b8548b80$28fda280$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcsHs6INGqGv+8e4RR6re4uHc5syvg== Content-Language: en-us X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.1 tagged_above=-10 required=5 tests=BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7 X-Spam-Level: X-Archive-Number: 201006/83 X-Sequence-Number: 34861 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