pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thorsten Glaser <tg@evolvis.org>
To: pgsql-general@postgresql.org
Subject: Re: "PANIC: could not open critical system index 2662" - twice
Date: Fri, 14 Apr 2023 06:00:22 +0200 (CEST)
Message-ID: <e6158ea-dcff-68a1-eef9-b24215d636e0@evolvis.org> (raw)
In-Reply-To: <8486f71f9c11e98af787e15e2d2ed0ecfdbf6ee7.camel@cybertec.at>
References: <01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000@eu-west-1.amazonses.com>
	<4f4ab16320d7b3a4e9950eaabde752dce204dc77.camel@cybertec.at>
	<010201877134be1c-fb837249-04a1-4cb0-a13f-c542425b50a0-000000@eu-west-1.amazonses.com>
	<ZDX87IYoz0GU9CKy@paquier.xyz>
	<010201877966fc0d-e09f5a0b-e846-417b-b30a-b8d57ac61fa3-000000@eu-west-1.amazonses.com>
	<c6a6f6c7a3e9a707ac7b28cefeca67d045ecc63a.camel@cybertec.at>
	<010201877c0423c8-0a35b03c-d274-4857-ba99-ff7ea51d676b-000000@eu-west-1.amazonses.com>
	<8486f71f9c11e98af787e15e2d2ed0ecfdbf6ee7.camel@cybertec.at>

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 :-)





view thread (65+ messages)  latest in thread

Message-ID: <e6158ea-dcff-68a1-eef9-b24215d636e0@evolvis.org>
Permalink:  ../e6158ea-dcff-68a1-eef9-b24215d636e0@evolvis.org/
Also on:    postgresql.org/message-id/e6158ea-dcff-68a1-eef9-b24215d636e0@evolvis.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tg@evolvis.org
  Subject: Re: "PANIC: could not open critical system index 2662" - twice
  In-Reply-To: <e6158ea-dcff-68a1-eef9-b24215d636e0@evolvis.org>
  References: <01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000@eu-west-1.amazonses.com> <4f4ab16320d7b3a4e9950eaabde752dce204dc77.camel@cybertec.at> <010201877134be1c-fb837249-04a1-4cb0-a13f-c542425b50a0-000000@eu-west-1.amazonses.com> <ZDX87IYoz0GU9CKy@paquier.xyz> <010201877966fc0d-e09f5a0b-e846-417b-b30a-b8d57ac61fa3-000000@eu-west-1.amazonses.com> <c6a6f6c7a3e9a707ac7b28cefeca67d045ecc63a.camel@cybertec.at> <010201877c0423c8-0a35b03c-d274-4857-ba99-ff7ea51d676b-000000@eu-west-1.amazonses.com> <8486f71f9c11e98af787e15e2d2ed0ecfdbf6ee7.camel@cybertec.at> <e6158ea-dcff-68a1-eef9-b24215d636e0@evolvis.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox