Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 9C8F1B5DBE9 for ; Sat, 16 Jul 2011 13:00:02 -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 36856-01 for ; Sat, 16 Jul 2011 15:59:55 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 38A08B5DBE6 for ; Sat, 16 Jul 2011 12:59:55 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p6GFxq7L027387; Sat, 16 Jul 2011 11:59:53 -0400 (EDT) To: Ken Caruso cc: "pgsql-admin@postgresql.org" Subject: Re: 9.0.4 Data corruption issue In-reply-to: References: Comments: In-reply-to Ken Caruso message dated "Sat, 16 Jul 2011 04:05:15 -0700" Date: Sat, 16 Jul 2011 11:59:52 -0400 Message-ID: <27386.1310831992@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=0.001 X-Spam-Level: X-Archive-Number: 201107/122 X-Sequence-Number: 37901 Ken Caruso writes: > Had a DB that had bloated due to lots of updates and insuffcient auto vacuum > settings. Attempted the following in the following order: > VACUUM VERBOSE full tablename; > CLUSTER tablename; > Did the full first to ensure that the cluster had enough space to run. > The db had already been previously clustered to an index. At some point > during the VACUUM I started seeing the following errors in the logs: > CONTEXT: writing block 12125253 of relation base/2651908/652397108 > WARNING: could not write block 12125253 of base/2651908/652397108 > DETAIL: Multiple failures --- write error might be permanent. Ummm .... what's the actual ERROR? regards, tom lane