From: | Dimitri Nagiev <dnagiev(at)gmx(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org, dmagiev(at)gmx(dot)de |
Subject: | Re: pg_dump: ERROR: cannot read block 1055 of summary: Input/output error |
Date: | 2003-06-28 10:22:58 |
Message-ID: | 19374.1056795778@www65.gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> Dimitri Nagiev <dnagiev(at)gmx(dot)de> writes:
> > using pg_dump I get the following error message:
> > pg_dump: ERROR: cannot read block 1055 of summary: Input/output error
> > calls from psql give me similar trouble:
> > ERROR: cannot read block 1055 of summary: Interrupted system call
>
> > There's a good backup from yesterday, but still I am very concerned.
>
> As you should be. It sounds like your disk has developed a bad sector.
> I'd recommend replacing the disk --- where one sector has gone bad,
> others may soon follow.
>
> regards, tom lane
>
thanks, yes it could be a hard disk issue, at least when I'm trying to zip
the whole psql directory I get the following message:
adding: pgsql/data/base/892124/937757 zip warning: file size changed
while zi (deflated 88%)
as the postmaster has been shut down, nobody should change files in the
pgsql directory tree.
rgds
dimitri
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Nagiev | 2003-06-28 11:58:49 | Re: pg_dump: ERROR: cannot read block 1055 of summary: Input/output error |
Previous Message | Tom Lane | 2003-06-28 03:12:46 | Re: pg_dump: ERROR: cannot read block 1055 of summary: Input/output error |