Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E20029FBCDE for ; Mon, 18 Jun 2007 17:25:29 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 13892-05 for ; Mon, 18 Jun 2007 17:25:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id EBF069FBCA9 for ; Mon, 18 Jun 2007 17:25:25 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l5IKPODn004714; Mon, 18 Jun 2007 16:25:24 -0400 (EDT) To: "Kevin Grittner" cc: pgsql-admin@postgresql.org Subject: Re: Explained by known hardware failures, or keep looking? In-reply-to: <467699B7.EE98.0025.0@wicourts.gov> References: <467699B7.EE98.0025.0@wicourts.gov> Comments: In-reply-to "Kevin Grittner" message dated "Mon, 18 Jun 2007 14:41:59 -0500" Date: Mon, 18 Jun 2007 16:25:24 -0400 Message-ID: <4713.1182198324@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/153 X-Sequence-Number: 25821 "Kevin Grittner" writes: > Could all of this be reasonably explained by the controller failure and/or = > the subsequent abrupt power loss, or should I be looking for another cause?= > Personally, as I look at this, I'm suspicious that either the controller = > didn't persist dirty pages in the June 14th failure That's what it looks like to me --- it's hard to tell if the hardware or the filesystem is at fault, but one way or another some pages that were supposedly securely down on disk were wiped to zeroes. You should probably review whether the hardware is correctly reporting write-complete. regards, tom lane