Re: bad block problem - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: bad block problem
Date
Msg-id 4EDFA52F0200002500043A8A@gw.wicourts.gov
Whole thread Raw
In response to bad block problem  (jkells <jtkells@verizon.net>)
Responses Re: bad block problem  (Craig Ringer <ringerc@ringerc.id.au>)
List pgsql-admin
jkells <jtkells@verizon.net> wrote:

> I tried to do a cold backup/copy
> cp  -r * ../data2/
>
> and received the following from cp
> cp: base/9221176/9221183: I/O error

That sounds like your storage system is failing, quite independently
from PostgreSQL.  Copy the entire data directory tree to some other
medium immediately, and preserve this copy.  If you hit bad blocks,
retry if possible.  If you just can't read some portions of it, you
need to get what you can, and make notes of any garbage or missed
portions of files.  Use the copy as a source to copy onto a reliable
storage system.

Without knowing more about what sort of storage system you're
talking about it is hard to give advice or predict whether it might
be fixable somehow.  If you try to run a database on failing
hardware, it will not be a pleasant experience.

-Kevin

pgsql-admin by date:

Previous
From: jkells
Date:
Subject: Re: bad block problem
Next
From: Walter Hurry
Date:
Subject: Re: bad block problem