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

Re: fdatasync failed, I/O error

From: Alvaro Herrera <alvherre(at)surnet(dot)cl>
To: "Brusser, Michael" <Michael(dot)Brusser(at)matrixone(dot)com>
Cc: 'Pgsql-Hackers' <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fdatasync failed, I/O error
Date: 2005-06-01 14:51:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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]>)
"The Gord often wonders why people threaten never to come back after they've
been told never to return" (

In response to

pgsql-hackers by date

Next:From: Jonah H. HarrisDate: 2005-06-01 14:53:13
Subject: Re: Google's Summer of Code ...
Previous:From: Tom LaneDate: 2005-06-01 14:47:05
Subject: Re: regarding storage in postgres

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