pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alban Hertroys <haramrae@gmail.com>
To: Evgeny Morozov <postgresql3@realityexists.net>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: PostgreSQL General <pgsql-general@postgresql.org>
Subject: Re: "PANIC: could not open critical system index 2662" - twice
Date: Fri, 14 Apr 2023 10:42:26 +0200
Message-ID: <A312EDE5-838F-4D81-BFA3-C269BAA3F68F@gmail.com> (raw)
In-Reply-To: <010201877eb3c125-d9aff979-cad6-407b-8b4e-012487666088-000000@eu-west-1.amazonses.com>
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>
	<010201877eb3c125-d9aff979-cad6-407b-8b4e-012487666088-000000@eu-west-1.amazonses.com>


> On 14 Apr 2023, at 9:38, Evgeny Morozov <postgresql3@realityexists.net> wrote:

(…)

> I don't know whether ZFS zero-fills blocks on disk errors. As I
> understood, ZFS should have been able to recover from disk errors (that
> were "unrecoverable" at the hardware level) using the data on the other
> two disks (which did not report any errors). Thus, PG should not have
> seen any corrupted data (if ZFS was working correctly).
> https://unix.stackexchange.com/questions/341614/understanding-the-error-reporting-of-zfs-on-linux
> seems to confirm this. Am I misunderstanding something?

Your problem coincides with a thread at freebsd-current with very similar data corruption after a recent OpenZFS import: blocks of all zeroes, but also missing files. So, perhaps these problems are related?

Apparently, there was a recent fix for a data corruption issue with the block_cloning feature enabled, but people are still seeing corruption even when they never enabled that feature.

I couldn’t really find the start of the thread in the archives, so this one kind of jumps into the middle of the thread at a relevant-looking point:

https://lists.freebsd.org/archives/freebsd-current/2023-April/003446.html

Regards,

Alban Hertroys
--
There is always an exception to always.









view thread (65+ messages)  latest in thread

Message-ID: <A312EDE5-838F-4D81-BFA3-C269BAA3F68F@gmail.com>
Permalink:  ../A312EDE5-838F-4D81-BFA3-C269BAA3F68F@gmail.com/
Also on:    postgresql.org/message-id/A312EDE5-838F-4D81-BFA3-C269BAA3F68F@gmail.com

 · 

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: haramrae@gmail.com, postgresql3@realityexists.net, laurenz.albe@cybertec.at
  Subject: Re: "PANIC: could not open critical system index 2662" - twice
  In-Reply-To: <A312EDE5-838F-4D81-BFA3-C269BAA3F68F@gmail.com>
  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> <010201877eb3c125-d9aff979-cad6-407b-8b4e-012487666088-000000@eu-west-1.amazonses.com> <A312EDE5-838F-4D81-BFA3-C269BAA3F68F@gmail.com>

* 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