Date: Sat, 9 Nov 2024 13:06:21 +0100 From: Palle Girgensohn <girgen@FreeBSD.org> To: void <void@f-m.fm> Cc: freebsd-fs@freebsd.org Subject: Re: zfs snapshot corruption when using encryption Message-ID: <E46FDA51-4FC5-4ABA-8E4C-6261869EB411@FreeBSD.org> In-Reply-To: <Zy7CB7trCVTD1fEv@int21h> References: <03E4CCF5-0F9A-4B0E-A9DA-81C7C677860C@FreeBSD.org> <Zy4XHlKodLu7utBa@int21h> <3E85AAAE-8B1E-47C7-B581-E3D98AB03907@FreeBSD.org> <Zy5kmpL_8dJh0AGZ@int21h> <F328561D-AD0A-475D-8E67-9DDD93468301@FreeBSD.org> <Zy7CB7trCVTD1fEv@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
> 9 nov. 2024 kl. 02:59 skrev void <void@f-m.fm>: >=20 > On Fri, Nov 08, 2024 at 11:11:23PM +0100, Palle Girgensohn wrote: >=20 >> $ freebsd-version -ku >> 14.0-RELEASE-p10 >> 14.0-RELEASE-p10 >>=20 >> dunno how to present in the above fashion? Binary install, not from = source. >=20 > % zfs version >=20 >> The latter, zfs per-filesystem zfs encryption. I haven't heard any = horror stories about it, albeit it's quite fresh code. >=20 > I'm wrong about native zfs encryption not being on 14.0. Seems like it = is. https://www.freebsd.org/releases/14.0R/relnotes/ >=20 > I'm reading this bit: >=20 > ### > ZFS Changes >=20 > OpenZFS has been upgraded to version 2.2. New features include: >=20 > block cloning, which allows shallow copies of blocks in file copies. = This is optional, and disabled by default; it can be enabled with sysctl = vfs.zfs.bclone_enabled=3D1. >=20 > scrub error log (zpool scrub -e) > BLAKE3 checksums, which are fast, and are now the recommended secure = checksums > corrective zfs receive can heal corrupted data vdev and zpool user = properties, similar to dataset user properties. > ### >=20 > Then again, 14.0 is EoL. >=20 >> Na, it's JBOD alright. I see nothing weird with the disks. >=20 >>> Reallocated_Sector_Ct >>> Reported_Uncorrect >>> Current_Pending_Sector >>> Offline_Uncorrectable >=20 > Were all these values '0' ? I don't see the props at all. >=20 > Using truss might give a clue about the failure: >=20 > # truss -o /tmp/truss.out zfs-send-commands >=20 > make sure the outfile is made in a place with lots of spare space. At present I don't have an error, had to remove the snapshot and run = zpool scrub -e, to get the zfs send propagation working. We see these = error popping up every other day, so I'll get a truss once we get the = next problematic snapshot. Box is updated to 14.1, FWIW. Palle
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E46FDA51-4FC5-4ABA-8E4C-6261869EB411>