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

No, this is the first time, I've seen this issue.In past as well reindex the tables and it works well.
BTW now I'm resetting the database to start from fresh.

Regards,
Mayank MittalBarco Electronics System Ltd.Mob. +91 9873437922

> From: andres(at)2ndquadrant(dot)com
> To: 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
> Date: Fri, 21 Sep 2012 13:43:00 +0200
> CC: tgl(at)sss(dot)pgh(dot)pa(dot)us; pgsql-bugs(at)postgresql(dot)org
>
> 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
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs