Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Mayank Mittal <mayank(dot)mittal(dot)1982(at)hotmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes
Date: 2012-09-21 11:43:00
Message-ID: 201209211343.00408.andres@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Friday, September 21, 2012 01:37:38 PM Mayank Mittal wrote:
> As discussed with Andres on IRC, I tried to reproduce the issue with some
> debug log enabled.In order to reproduce I fixed my already broken system
> (index corrupted) by running REINDEX database <database_name>.Once done I
> performed the failover and now I'm getting following
> error:[org.postgresql.util.PSQLException: ERROR: missing chunk number 0
> for toast value 33972 in pg_toast_16582]
Unfortunately I don't think its really a valid approach to start from an
already corrupted database when doing this :( There might already be lingering
corruption causing the problem.

Have you seen the missing chunk error before? Did you reproduce the issue from
a corrupted database as well before?

Greetings,

Andres

> Regards,
> Mayank MittalBarco Electronics System Ltd.Mob. +91 9873437922
>
> > Date: Fri, 21 Sep 2012 11:34:49 +0200
> > From: mailings(at)oopsware(dot)de
> > To: andres(at)2ndquadrant(dot)com
> > CC: tgl(at)sss(dot)pgh(dot)pa(dot)us; pgsql-bugs(at)postgresql(dot)org;
> > mayank(dot)mittal(dot)1982(at)hotmail(dot)com Subject: Re: [BUGS] BUG #7562: could not
> > read block 0 in file "base/16385/16585": read only 0 of 8192 bytes
> >
> >
> >
> > --On 21. September 2012 10:25:50 +0200 Andres Freund
> >
> > <andres(at)2ndquadrant(dot)com> wrote:
> > >> We had a similar issue at a customer site. The server was shut down
> > >> for updating it from 9.1.4 to 9.1.5, after starting it again the log
> > >> was immediately cluttered with
> > >
> > > How was it shutdown? -m fast or -m immediate?
> >
> > -m fast
> >
> > >> ERROR: could not read block 251 in file "base/6447890/7843708": read
> > >> only 0 of 8192 bytes
> > >
> > > So, not block 0. How many blocks does the new index contain?
> >
> > 255 blocks according to its current size.

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mayank Mittal 2012-09-21 11:48:42 Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes
Previous Message Amit kapila 2012-09-21 11:18:01 Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown