Date: Fri, 2 Dec 2022 07:58:47 +0100 From: Andrea Venturoli <ml@netfence.it> To: questions@freebsd.org Subject: Re: ZFS Permanent error <0xffffffffffffffff>:<0x0> Message-ID: <a5aabc02-52de-7fe3-4a34-9c305d54135d@netfence.it> In-Reply-To: <624e3234-39ec-b2c3-02e9-edc52aaa02d1@freebsd.org> References: <0ddaa537-ffa9-af0d-1a5a-1874a67ed2b5@netfence.it> <624e3234-39ec-b2c3-02e9-edc52aaa02d1@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/2/22 00:21, Graham Perrin wrote: > Can something like this be a valid command? > > zdb -d <0xffffffffffffffff>:<0x0> # zdb -d "<0xffffffffffffffff>:<0x0>" zdb: can't open '<0xffffffffffffffff>:<0x0>': No such file or directory > Also, taking a hint from <https://github.com/openzfs/zfs/issues/3476>; and <https://github.com/openzfs/zfs/issues/4736>; (but not assuming a hardware issue in your case): I had read those, but they didn't add much. I also read https://github.com/openzfs/zfs/issues/3094: maybe I don't understand it fully, but it didn't lead to any definitive solution. > zdb -mc zroo2 Thìs didn't fix the error. Do you want me to copy all the output here? And yes, I see some leaked space (see #3094), but I'm not sure the two issues are related. bye & Thanks av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a5aabc02-52de-7fe3-4a34-9c305d54135d>