Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Dec 2022 16:50:09 +0100
From:      Andrea Venturoli <ml@netfence.it>
To:        sysadmin.lists@mailfence.com
Cc:        questions@freebsd.org
Subject:   Re: ZFS Permanent error <0xffffffffffffffff>:<0x0>
Message-ID:  <2d897f57-5bdc-7497-d374-e7a536d9a440@netfence.it>
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 11/30/22 07:54, Sysadmin Lists wrote:

> IIRC, snapshots are valid entries. Perhaps the corrupted file is still
> associated with other snapshots. You might need to use `zdb' to find it and
> delete it from the filesystem

Thanks for your explanation, but this is beyond my skills currently 
(i.e. unless I find a good tutorial on zdb).
What should I be looking for?

If the file is associated to another snapshot, why doesn't it say the 
name of this snapshot, instead of the deleted one?

In any case, you are saying my storage isn't exploding and I can live 
with this harmless warning?
If it's so, well, maybe it will go away someday as older automatical 
snapshots are deleted.

  bye & Thanks
	av.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2d897f57-5bdc-7497-d374-e7a536d9a440>