Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 02C8C2E00E8 for ; Wed, 13 Feb 2008 17:39:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 03989-04 for ; Wed, 13 Feb 2008 17:39:50 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 6B3F92E00CF for ; Wed, 13 Feb 2008 17:39:50 -0400 (AST) 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 m1DLdlcV024013; Wed, 13 Feb 2008 16:39:47 -0500 (EST) To: "Thomas F. O'Connell" cc: pgsql-admin@postgresql.org Subject: Re: Block Read Error: Success? In-reply-to: <7DF13FAE-CE2F-406C-98D6-2003D2BED624@o.ptimized.com> References: <7DF13FAE-CE2F-406C-98D6-2003D2BED624@o.ptimized.com> Comments: In-reply-to "Thomas F. O'Connell" message dated "Wed, 13 Feb 2008 15:21:08 -0600" Date: Wed, 13 Feb 2008 16:39:47 -0500 Message-ID: <24012.1202938787@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/165 X-Sequence-Number: 28239 "Thomas F. O'Connell" writes: > A few days ago, we began seeing this error in our logs: > ERROR: could not read block [redacted] of relation [redacted]: Success > I've encountered "could not read block" errors in other databases in > the past, but have never witnessed the "Success" tag at the end. What > does that mean? What this means is a read past EOF --- that is, read() returned fewer bytes than requested (perhaps none at all) but did not signal an error. A potential ultimate cause is corrupt indexes that contain pointers leading past the end of the table. Which sounds a whole lot like the VACUUM bug fixed in 8.0.14 and other recent releases. > We're running 8.0.13 on FC3. Is there any reason not to suspect the > hardware at this point? I'd question your choice of platform --- FC3 went EOL quite some time ago. regards, tom lane