Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pnAct-0008Fh-U8 for pgsql-general@arkaria.postgresql.org; Fri, 14 Apr 2023 04:01:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pnAbt-0006Rv-Nc for pgsql-general@arkaria.postgresql.org; Fri, 14 Apr 2023 04:00:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pnAbt-0006Rl-DK for pgsql-general@lists.postgresql.org; Fri, 14 Apr 2023 04:00:29 +0000 Received: from evolvis.org ([217.144.135.11]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pnAbq-002mTz-O5 for pgsql-general@postgresql.org; Fri, 14 Apr 2023 04:00:28 +0000 Received: from x61w.mirbsd.org (2001-4dd7-b4e-0-21f-3bff-fe0d-cbb1.ipv6dyn.netcologne.de [IPv6:2001:4dd7:b4e:0:21f:3bff:fe0d:cbb1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) by evolvis.org (Postfix) with ESMTPSA id E795E100955 for ; Fri, 14 Apr 2023 04:00:24 +0000 (UTC) Received: by x61w.mirbsd.org (Postfix, from userid 1000) id D581260930; Fri, 14 Apr 2023 06:00:22 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by x61w.mirbsd.org (Postfix) with ESMTP id D000B60432 for ; Fri, 14 Apr 2023 06:00:22 +0200 (CEST) Date: Fri, 14 Apr 2023 06:00:22 +0200 (CEST) From: Thorsten Glaser To: pgsql-general@postgresql.org Subject: Re: "PANIC: could not open critical system index 2662" - twice In-Reply-To: <8486f71f9c11e98af787e15e2d2ed0ecfdbf6ee7.camel@cybertec.at> Message-ID: 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> <010201877966fc0d-e09f5a0b-e846-417b-b30a-b8d57ac61fa3-000000@eu-west-1.amazonses.com> <010201877c0423c8-0a35b03c-d274-4857-ba99-ff7ea51d676b-000000@eu-west-1.amazonses.com> <8486f71f9c11e98af787e15e2d2ed0ecfdbf6ee7.camel@cybertec.at> Content-Language: de-DE-1901 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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=E2=80=99t 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 --=20 15:41=E2=8E=9C Somebody write a testsuite for hello= world :-)