| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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:44:30 |
| Message-ID: | 13942.1117637070@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Brusser, Michael" <Michael(dot)Brusser(at)matrixone(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-01 14:47:05 | Re: regarding storage in postgres |
| Previous Message | Dawid Kuroczko | 2005-06-01 14:43:44 | Re: NOLOGGING option, or ? |