Re: Invalid Page Header Error - Mailing list pgsql-general

From Albe Laurenz
Subject Re: Invalid Page Header Error
Date
Msg-id A737B7A37273E048B164557ADEF4A58B17C4A4EE@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: Invalid Page Header Error  (Carlo Curatolo <genamiga@brutele.be>)
Responses Re: Invalid Page Header Error  (Carlo Curatolo <genamiga@brutele.be>)
List pgsql-general
Carlo Curatolo wrote:
> When I lauch a vacuumdb, I have an error :  ERREUR: en-tête de page invalide
> dans le bloc 39639 de la relation base/16384/599662
> 
> With a
> SELECT * FROM  pg_catalog.pg_largeobject
> 
> Result is
> ERREUR: en-tête de page invalide dans le bloc 39639 de la relation
> base/16384/599662
> 
> I suppose that the data of LargeObject 599662 are corrupted...

That is not the OID of a large object, but of a table.

What do you get for
SELECT oid, relname, relkind FROM pg_class WHERE relfilenode = 599662;

> Question is : How I could I know where this LargeObject is used ?
> 
> I can, of course, use the "zero_damaged_pages = on" option in
> postgresql.conf. Then dump/restore.
> But in this case I didn't know where this corrupted LargeObject is used...

That could result in *all* your large objects or something else
to get destroyed...

You have some kind of data corruption.
Have there been any crashes or unusual occurrences lately?

The best thing would be to check your hardware thoroughly
and restore the database from a backup.

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: Stop execution without ERROR
Next
From: Carlo Curatolo
Date:
Subject: Re: Invalid Page Header Error