Thread: pg_dump: ERROR: cannot read block 1055 of summary: Input/output error
Hi all, using pg_dump I get the following error message: pg_dump stats > stats.sql pg_dump: ERROR: cannot read block 1055 of summary: Input/output error pg_dump: lost synchronization with server, resetting connection pg_dump: SQL command to dump the contents of table "summary" failed: PQendcopy() failed. pg_dump: Error message from server: pg_dump: The command was: COPY public.summary (id, timestamp, user, keyfigure, total, absolutedifference, relativedifference) TO stdout; calls from psql give me similar trouble: # select count(*) from summary; ERROR: cannot read block 1055 of summary: Interrupted system call some more info: - we are using postgresql 7.3.2 - before the problems, the table had approx. 200.000 records without any problems - a regular import is (was) feeding about 500 records a day into the table. There's a good backup from yesterday, but still I am very concerned. Any ideas on how to fix the problem ? Any reasons why it does occur ? thanks -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
Dimitri Nagiev <dnagiev@gmx.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
> Dimitri Nagiev <dnagiev@gmx.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!
yes, it was a problem with the hard disk. thanks & best regards dimitri -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!