Date: Sun, 26 Sep 2021 00:52:59 -0400 From: Rich <rincebrain@gmail.com> To: Zaphod Beeblebrox <zbeeble@gmail.com> Cc: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: ZFS errors with two HEX numbers. Message-ID: <CAOeNLupMJ179d_EgnTAcd0khEDZJGSscP=M8k1CCWkBzKzaKBg@mail.gmail.com> In-Reply-To: <CACpH0MeGdYsoKd%2B4DruiY-ifeTfeDOvWOTFX9qTNGc8NKt5HBg@mail.gmail.com> References: <CACpH0MeUsu9v3iVukEqVXZq_p5BDwmqzxoED=QA4JmOCek_JJg@mail.gmail.com> <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> <CACpH0MeGdYsoKd%2B4DruiY-ifeTfeDOvWOTFX9qTNGc8NKt5HBg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't have a testpool handy to confirm it, but I would expect you to be able to do something like zdb -ddddd [pool]/[objsetid in hex] [objectid in hex] e.g. zdb -ddddd vr1/0x57b2 0x73ab46 Or failing that, drop the object id (and then probably some of the -d, that gets real verbose). - Rich On Sun, Sep 26, 2021 at 12:27 AM Zaphod Beeblebrox <zbeeble@gmail.com> wrote: > > How do I find which snapshot it's in? > > On Sat, Sep 25, 2021 at 6:01 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > > > > > I have seen this in the past. It was corruption on some deleted file > > preserved on snapshot. Once I deleted snapshots this error disappeared. > > > > [...] > > > > Miroslav Lachman > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOeNLupMJ179d_EgnTAcd0khEDZJGSscP=M8k1CCWkBzKzaKBg>