Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id C67662E00FE for ; Wed, 13 Feb 2008 17:21:17 -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 97371-05 for ; Wed, 13 Feb 2008 17:21:12 -0400 (AST) Received: from howe.textdrive.com (howe.textdrive.com [207.7.108.240]) by postgresql.org (Postfix) with ESMTP id AA64D2E00E8 for ; Wed, 13 Feb 2008 17:21:12 -0400 (AST) Received: from [192.168.5.133] (74.223.106.45.nw.nuvox.net [74.223.106.45]) by howe.textdrive.com (Postfix) with ESMTP id 8D1D6125541 for ; Wed, 13 Feb 2008 21:21:10 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v753) To: pgsql-admin@postgresql.org Message-Id: <7DF13FAE-CE2F-406C-98D6-2003D2BED624@o.ptimized.com> Content-Type: multipart/alternative; boundary=Apple-Mail-33--855314571 From: "Thomas F. O'Connell" Subject: Block Read Error: Success? Date: Wed, 13 Feb 2008 15:21:08 -0600 X-Mailer: Apple Mail (2.753) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/163 X-Sequence-Number: 28237 --Apple-Mail-33--855314571 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed 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? The error went unnoticed until, ultimately, significant parts of a database-driven website were not able to be read. Backups had been collected for days using pg_dump (which is configured to output SQL), and we were able to restore from a backup created earlier on the day that the content became unavailable. After restoration from backup, we haven't seen the errors again. We're running 8.0.13 on FC3. Is there any reason not to suspect the hardware at this point? -- Thomas F. O'Connell optimizing modern web applications : for search engines, for usability, and for performance : http://o.ptimized.com/ 615-260-0005 --Apple-Mail-33--855314571 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 A few days ago, we began seeing this error in our logs:

ERROR: =A0could 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?

The = error went unnoticed until, ultimately, significant parts of a = database-driven website were not able to be read. Backups had been = collected for days using pg_dump (which is configured to output SQL), = and we were able to restore from a backup created earlier on the day = that the content became unavailable. After restoration from backup, we = haven't seen the errors again.

We're running 8.0.13 on = FC3. Is there any reason not to suspect the hardware at this = point?

optimizing modern web = applications
: for search engines, for usability, and for = performance :

615-260-000= 5
=

= --Apple-Mail-33--855314571--