Re: [HACKERS] fdatasync failed, I/O error

2005-06-01 Thread Tom Lane 
Brusser, Michael [EMAIL PROTECTED] writes:
 Our customer is running Postgresql v. 7.3.4 on Linux(Redhat 3.0 Ent.)
 The application crashed and I am trying to understand what could have caused
 this kind of problems:

fdatasync of log file 0, segment 2 failed: input/output error
PGSTAT: Error closing temp stats file 
   .../.../postgresql/global/pgstat.tmp.10278: Input/output error

input/output error definitely means a hardware problem ... you might
try looking in the kernel logs (/var/log/messages) to see if any
additional information got recorded there.

regards, tom lane

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

Re: [HACKERS] fdatasync failed, I/O error

2005-06-01 Thread Alvaro Herrera 
On Wed, Jun 01, 2005 at 10:27:04AM -0400, Brusser, Michael wrote:
 
 Our customer is running Postgresql v. 7.3.4 on Linux(Redhat 3.0 Ent.)
 The application crashed and I am trying to understand what could have caused
 this kind of problems:
 
fdatasync of log file 0, segment 2 failed: input/output error
PGSTAT: Error closing temp stats file 
   .../.../postgresql/global/pgstat.tmp.10278: Input/output error
 
 I suppose they could be using NFS (I know, I know... we have to deal with
 that. But could it be something else? A bad disk?)

Bad disk, bad controller, bad cable between the two, are some which come
to mind.

-- 
Alvaro Herrera (alvherre[a]surnet.cl)
The Gord often wonders why people threaten never to come back after they've
been told never to return (www.actsofgord.com)

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq