Skip site navigation (1) Skip section navigation (2)

Re: Block Read Error: Success?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas F(dot) O'Connell" <tf(at)o(dot)ptimized(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Block Read Error: Success?
Date: 2008-02-13 21:39:47
Message-ID: 24012.1202938787@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Thomas F. O'Connell" <tf(at)o(dot)ptimized(dot)com> 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

In response to

pgsql-admin by date

Next:From: Scott MarloweDate: 2008-02-13 21:41:10
Subject: Re: terminating connection because of crash of another server process
Previous:From: Thomas F. O'ConnellDate: 2008-02-13 21:21:08
Subject: Block Read Error: Success?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group