Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 5160C133798E for ; Fri, 18 Feb 2011 11:17:45 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 62512-10 for ; Fri, 18 Feb 2011 15:17:38 +0000 (UTC) X-Greylist: delayed 00:05:18.947616 by SQLgrey-1.7.6 Received: from mail.starpoint.com (mail.starpoint.com [64.190.10.4]) by mail.postgresql.org (Postfix) with ESMTP id C72941336FA7 for ; Fri, 18 Feb 2011 11:17:37 -0400 (AST) X-Virus-Scanned: amavisd-new at starpoint.com Received: from mail.starpoint.com ([127.0.0.1]) by localhost (mail.starpoint.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDhmu64jqd8M for ; Fri, 18 Feb 2011 10:12:16 -0500 (EST) Received: from [192.168.45.105] (ool-44c032af.dyn.optonline.net [68.192.50.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.starpoint.com (Postfix) with ESMTPSA id 4F45B302F349 for ; Fri, 18 Feb 2011 10:12:16 -0500 (EST) From: Tony Nelson Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Corrupted disk Date: Fri, 18 Feb 2011 10:12:16 -0500 Message-Id: <2B07A451-9F67-4438-8802-B10F46FDAF2E@starpoint.com> To: pgsql-admin@postgresql.org Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201102/175 X-Sequence-Number: 36814 Good morning all, This morning my server (ubuntu 10.04 LTS, pg 8.4 from apt) experienced = a disk corruption which caused errors like this: Feb 18 08:50:07 ihdb1 postgres[13317]: [2-1] user=3Dpostgres,db=3Dinstihir= e ERROR: invalid page header in block 10 of relation base/16384/8082305 I am ok, because I have a dump from last night, and wal since then. =20 As a test, I tried doing a dump like this from the broken server: pg_dump -Fc mydb > busted.dump I restored this dump on a test server, and all of the data looks ok, and = my application is able to run the operation that was failing in = production just fine. My question is simple, is my dump good? Is it possible that pg_dump = was able to correctly save the data that "select .. " and "update.. " = couldn't. Can I drop/create/restore from this dump? Or should I restore from last = nights full and apply the WAL? Thanks for any help. Tony Nelson Starpoint Solutions=