Date: Tue, 29 Nov 2022 06:27:17 +0100 (CET) From: Sysadmin Lists <sysadmin.lists@mailfence.com> To: questions@freebsd.org Cc: Andrea Venturoli <ml@netfence.it> Subject: Re: ZFS Permanent error <0xffffffffffffffff>:<0x0> Message-ID: <255658040.26515.1669699637761@orville.co-bxl> In-Reply-To: <5def1695-82b3-3441-c11a-d64ca0c7c30a@netfence.it> References: <0ddaa537-ffa9-af0d-1a5a-1874a67ed2b5@netfence.it> <c4d43906-d8a7-8945-abab-4e6c81e2fc6f@freebsd.org> <5def1695-82b3-3441-c11a-d64ca0c7c30a@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
> ---------------------------------------- > From: Andrea Venturoli <ml@netfence.it> > Sent: Mon Nov 28 09:39:24 CET 2022 > To: <questions@freebsd.org> > Subject: Re: ZFS Permanent error <0xffffffffffffffff>:<0x0> > > > What's that "<0x............>:<0x....>" supposed to mean? Some sort of > address/location, I suppose. But how do I interpret it? > > bye > av. > The construct is <dataset>:<filename>. It looks like you deleted the dataset the corrupted file was found on, so now ZFS displays it as that string. Bottom of the page here: https://docs.oracle.com/cd/E19253-01/819-5461/gbctx/index.html You can check `zpool history' for what it was called. -- Sent with https://mailfence.com Secure and private email
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?255658040.26515.1669699637761>