Date: Wed, 30 Nov 2022 09:00:41 +0000 From: Steve O'Hara-Smith <steve@sohara.org> To: Sysadmin Lists <sysadmin.lists@mailfence.com> Cc: questions@freebsd.org, Andrea Venturoli <ml@netfence.it> Subject: Re: ZFS Permanent error <0xffffffffffffffff>:<0x0> Message-ID: <20221130090041.83a3909ed4bfb6b3b0d617dd@sohara.org> In-Reply-To: <597333482.1125294.1669791240602@ichabod.co-bxl> References: <0ddaa537-ffa9-af0d-1a5a-1874a67ed2b5@netfence.it> <c4d43906-d8a7-8945-abab-4e6c81e2fc6f@freebsd.org> <5def1695-82b3-3441-c11a-d64ca0c7c30a@netfence.it> <255658040.26515.1669699637761@orville.co-bxl> <47265e09-3aa0-24fa-22cb-56e09bb524f0@netfence.it> <597333482.1125294.1669791240602@ichabod.co-bxl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 30 Nov 2022 07:54:00 +0100 (CET) Sysadmin Lists <sysadmin.lists@mailfence.com> wrote: > 1. If the file metadata is intact, it shows the full mount path to the > file: /path/to/filename > > 2. If the metadata is corrupted but the dataset still exists, it shows > this: full/dataset/name:<object number> > > 3. If the dataset has been deleted, it shows this: > <dataset number>:<object number> > or > '<metadata>':<object number> Right but what the OP sees is <-1>:<0> which rather implies that neither dataset nor object number exist now. It appears to be corruption in a place that is no longer used - clearing the error message and running a scrub is the right thing to do. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221130090041.83a3909ed4bfb6b3b0d617dd>