Re: could not read block 0 in file Error - Mailing list pgsql-admin

From Karl Denninger
Subject Re: could not read block 0 in file Error
Date
Msg-id 03f85c0a-8eeb-22e2-8459-72d56d58b48e@denninger.net
Whole thread Raw
In response to could not read block 0 in file Error  (Sbob <sbob@quadratum-braccas.com>)
List pgsql-admin
On 4/22/2022 16:23, Sbob wrote:

Hi all;


We had an issue with a PostgreSQL v12 cluster. Not sure all of the history as I was pulled in late, however we were seeing that the db would not start due to WAL inconsistencies, was throwing an error about could not find wal records.

So we ran a pg_resetwal -f -D [data dir]


we are dumping (via pg_dump) all the databases in the broken cluster and I will restore them to a new cluster,

however in one of the databases, for one of the tables we are getting this:


pg_dump: error: Dumping the contents of table "bigtable" failed: PQgetResult() fai
led.
pg_dump: error: Error message from server: ERROR:  could not read block 0 in file "base/6328739/6340053": read only 0 of 8192 bytes
pg_dump: error: The command was: COPY public.bigtable (recordid, containerid, record_type, description, overlaygroup) TO stdout;

Is there any way to recover?

Is the file physically there and can you "cat" it to /dev/null?  It's hard to read what doesn't exist or produces a hard error from the filesystem (e.g. disk error.)

--
Karl Denninger
karl@denninger.net
The Market Ticker
[S/MIME encrypted email preferred]
Attachment

pgsql-admin by date:

Previous
From: Sbob
Date:
Subject: could not read block 0 in file Error
Next
From: Laurenz Albe
Date:
Subject: Re: could not read block 0 in file Error