X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 6D8F811F6937 for ; Wed, 19 Apr 2006 19:33:11 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 required=5 tests=[none] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id vBqstq0l3Gew for ; Wed, 19 Apr 2006 19:33:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mailscan1.textdrive.com (mailscan1.textdrive.com [207.7.108.214]) by postgresql.org (Postfix) with ESMTP id 1032111F6947 for ; Wed, 19 Apr 2006 19:33:06 -0300 (ADT) Received: from webmail.textdrivehosting.com (webmail2.textdrive.com [10.0.0.194]) by mailscan1.textdrive.com (Postfix) with SMTP id B3ADC147C2B for ; Wed, 19 Apr 2006 22:31:58 +0000 (GMT) Received: from 10.0.0.7 (auth. user tfo@chilco.textdrive.com) by webmail.textdrivehosting.com with HTTP; Wed, 19 Apr 2006 22:31:14 +0000 To: pgsql-admin@postgresql.org Subject: Re: Invalid Page Headers Date: Wed, 19 Apr 2006 22:31:14 +0000 X-Mailer: IlohaMail/0.8.14 (On: webmail.textdrivehosting.com) Message-ID: From: "Thomas F. O'Connell" Bounce-To: "Thomas F. O'Connell" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archive-Number: 200604/190 X-Sequence-Number: 21359 On Apr 18, 2006, at 2:15 PM, Tom Lane wrote: "Thomas F. O'Connell" writes: I would've expected the RAID to protect postgres from the possibility of data corruption, but I guess not. Ooops :-(. It might be interesting to get pg_filedump dumps of the corrupted pages, just to see what the failure pattern looks like. I doubt there's much we can do about it, but you don't know till you look. ("If we knew what it was we were doing, it wouldn't be research.") Any tips on turning "ERROR: invalid page header in block 34 of relation" into a pg_filedump command that would yield something useful or interesting? If so, I'll post the results of all three relations known to be corrupt so far. Also, are there any questions I could be asking vendors (Dell, LSI) that would help sort out how the RAID contributed to corruption on disk? -- Thomas F. O'Connell Database Architecture and Programming Sitening, LLC http://www.sitening.com/ 3004 B Poston Avenue Nashville, TN 37203-1314 615-260-0005 (cell) 615-469-5150 (office) 615-469-5151 (fax)