Unexpected data beyond EOF during heavy writes
in [PgSql]
|
Prev: pg_upgrade - link mode and transaction-wraparound data loss
Next: [HACKERS] BYTEA / DBD::Pg change in 9.0 beta
From: Alvaro Herrera on 18 May 2010 16:35 Excerpts from Tony Sullivan's message of mar may 18 13:19:13 -0400 2010: > Hello everyone, > > We are seeing the following error message occasionally in the postgres logs: > > 2010-05-13 23:49:03 PDT ERROR: unexpected data beyond EOF in block 4106698 of relation "custom_discoveryprofile" > 2010-05-13 23:49:03 PDT HINT: This has been seen to occur with buggy kernels; consider updating your system. What's your storage? -- -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Alvaro Herrera on 20 May 2010 17:19 Excerpts from Tony Sullivan's message of jue may 20 16:54:17 -0400 2010: > > Hello everyone, > > > > > > We are seeing the following error message occasionally in the postgres logs: > > > > > > 2010-05-13 23:49:03 PDT ERROR: unexpected data beyond EOF in block 4106698 of relation "custom_discoveryprofile" > > > 2010-05-13 23:49:03 PDT HINT: This has been seen to occur with buggy kernels; consider updating your system. > > What's your storage? This was added here http://archives.postgresql.org/message-id/20060925220110.76B6A9FB251(a)postgresql.org in response to these two: http://thread.gmane.org/gmane.comp.db.postgresql.admin/18807 http://thread.gmane.org/gmane.comp.db.postgresql.general/74532 We (at Command Prompt) researched this recently for another setup and the common point you both have is NetApp. I then wondered about a bug in NetApp driver or NFS client implementation. -- -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Rosser Schwarz on 20 May 2010 17:38 On Thu, May 20, 2010 at 3:19 PM, Alvaro Herrera <alvherre(a)alvh.no-ip.org> wrote: > We (at Command Prompt) researched this recently for another setup and > the common point you both have is NetApp. I then wondered about a bug > in NetApp driver or NFS client implementation. It's definitely not (just) NetApp, though it may be their NFS -- or NFS in general; I couldn't say. I can't speak to their NFS implementation, beyond having generally heard good things about it, but I've run PostgreSQL on filers for years, and have never seen that message. Granted, I've only been iSCSI- or fibre-attached (or had the storage path abstracted away by some form of virtualization), so I haven't seen every possible use-case. In general, though, I'd be pretty wary of running postgres on an NFS mount. I know a lot of people run Oracle that way, but at the filesystem level, there are some vast differences between the two. Has anyone ever seen this message on non-NetApp NFS? rls -- :wq -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 20 May 2010 18:21
Rosser Schwarz <rosser.schwarz(a)gmail.com> writes: > Has anyone ever seen this message on non-NetApp NFS? It's been seen on non-NFS storage: http://archives.postgresql.org/pgsql-admin/2006-09/msg00096.php I don't believe we implicated NFS in the other original report, either. However, it's certainly possible that there's a similar bug in the NFS stack too on some platforms. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |