Re: ERROR: could not read block 4 ...

From: Leonardo M(dot) Ramé <l(dot)rame(at)griensu(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: ERROR: could not read block 4 ...
Date: 2016-09-15 14:11:28
Message-ID: 04256454-30be-9f49-60d1-fb5e34c1dca7@griensu.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

El 15/09/16 a las 11:05, Tom Lane escribió:
> "=?UTF-8?Q?Leonardo_M._Ram=c3=a9?=" <l(dot)rame(at)griensu(dot)com> writes:
>> Hi, I'm getting this error:
>> 2016-09-15 09:35:24 ART [13984-1] ERROR: could not read block 4 in file
>> "base/12210/11965": Error de entrada/salida
> That looks like a hardware problem ... might want to budget for a new disk
> sometime soon, before failures become more prevalent.
>
>> 1) Is this caused by a bad block?, can fsck fix it?.
> yes, and fsck is unlikely to help, though you could try.
>
>> 2) Is there a way to re-generate template0?.
> If you've never modified template1, you could drop template0 and re-create
> it from template1. Otherwise, pg_dumpall/initdb/reload would seem to be
> called for. A cautious person might want to do the latter anyway in case
> there's more problems than just this one.
>
> regards, tom lane

Thanks, indeed, I'm moving the Db to another server.

--
Leonardo M. Ramé
Medical IT - Griensu S.A.
Av. Colón 636 - Piso 8 Of. A
X5000EPT -- Córdoba
Tel.: +54(351)4246924 +54(351)4247788 +54(351)4247979 int. 19
Cel.: +54 9 (011) 40871877

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alex Sviridov 2016-09-15 14:57:55 Test letter
Previous Message Tom Lane 2016-09-15 14:05:31 Re: ERROR: could not read block 4 ...