Solaris 10 Sparc System NFS mounting the database directory from a NetApp
2020 NAS device.
ERROR: unexpected data beyond EOF in block 315378 of relation "file"
HINT: This has been seen to occur with buggy kernels; consider updating
Occasionally under heavy insert load.
The error comes from line 225 of bufmgr.c. The kernel bug mentioned in the
comments is an lseek bug in a Linux kernel so I don't believe that is the
The question is can anyone more familiar with this tell me what's going on
here? I don't know if this is a Postgres, Sun, or NetApp issue. Could it
be a work around for an old Linux bug causing an issue with acceptable
behavior of the NetApp device?
There has been some clock differences between the Solaris system and the
Netapp device. Could postgres be confused by file modify times being in the
future by a few seconds?
View this message in context: http://www.nabble.com/ERROR%3A--unexpected-data-beyond-EOF-in-block-XXXXX-of-relation-%22file%22-tp19680438p19680438.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2008-09-26 01:54:31|
|Subject: Re: BUG #4436: (E'\\' LIKE E'\\') => f |
|Previous:||From: Alex Hunsaker||Date: 2008-09-25 22:07:23|
|Subject: Re: Incorrect "invalid AM/PM string" error from to_timestamp|