Date: Tue, 29 Nov 2022 09:28:57 +0100 From: Andrea Venturoli <ml@netfence.it> To: questions@freebsd.org Subject: Re: ZFS Permanent error <0xffffffffffffffff>:<0x0> Message-ID: <c2b103d2-6b5e-6d89-03b0-7b3c18b7384a@netfence.it> In-Reply-To: <985efd90-81cc-783e-d8ca-af048f683343@holgerdanske.com> References: <0ddaa537-ffa9-af0d-1a5a-1874a67ed2b5@netfence.it> <985efd90-81cc-783e-d8ca-af048f683343@holgerdanske.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/29/22 02:43, David Christensen wrote: > I agree that "<0xffffffffffffffff>:<0x0>" does not look like a file name > -- it looks like a signed 64-bit integer value of -1 expressed in > hexadecimal with less-than and greater-than delimiters, followed by a > colon, followed by 0 expressed in hexadecimal with the same delimiters. Like an address into the spacemap? Only, I don't think such a location exists. > But, AIUI, Unix filenames can contain any characters except NUL. So, > there could be a file with that name somewhere on your system. I > suggest looking for the file using find(1); if only as a sanity check. > Be sure to check ".zfs/snapshot" directories also. No file by this name, nowhere. bye & Thanks anyway av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c2b103d2-6b5e-6d89-03b0-7b3c18b7384a>