From: | Thorsten Glaser <tg(at)evolvis(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
Date: | 2023-04-14 04:00:22 |
Message-ID: | e6158ea-dcff-68a1-eef9-b24215d636e0@evolvis.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 14 Apr 2023, Laurenz Albe wrote:
>So if your disk replaces a valid block with zeros (filesystem check
>after crash?), that could explain what you see.
Oh, I had that happen on a RAID 1 once. On of the two discs had an
intermittent error (write I guess) but didn’t fail out of the RAID,
and some of the reads from there got zero-filled blocks in some
positions. It was a CVS repository so I was able to identify all such
blocks in question and restore them from the rsync slave (whose initial
population predated the HDD issue).
Hm, now that I think about it, it could even have been a read error
with subsequent block reassignment. Oh well.
Filesystem issues (ext3, and ext4 without/predating auto_da_alloc,
in particular) could be it just as well of course.
bye,
//mirabilos
--
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2023-04-14 07:36:54 | Re: Support logical replication of DDLs |
Previous Message | Laurenz Albe | 2023-04-14 02:55:50 | Re: "PANIC: could not open critical system index 2662" - twice |