Date: Sat, 9 Nov 2024 01:59:35 +0000 From: void <void@f-m.fm> To: freebsd-fs@freebsd.org Subject: Re: zfs snapshot corruption when using encryption Message-ID: <Zy7CB7trCVTD1fEv@int21h> In-Reply-To: <F328561D-AD0A-475D-8E67-9DDD93468301@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 08, 2024 at 11:11:23PM +0100, Palle Girgensohn wrote: >$ freebsd-version -ku >14.0-RELEASE-p10 >14.0-RELEASE-p10 > >dunno how to present in the above fashion? Binary install, not from source. % zfs version >The latter, zfs per-filesystem zfs encryption. I haven't heard any horror >stories about it, albeit it's quite fresh code. I'm wrong about native zfs encryption not being on 14.0. Seems like it is. https://www.freebsd.org/releases/14.0R/relnotes/ I'm reading this bit: ### ZFS Changes OpenZFS has been upgraded to version 2.2. New features include: 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=1. 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. ### Then again, 14.0 is EoL. >Na, it's JBOD alright. I see nothing weird with the disks. >> Reallocated_Sector_Ct >> Reported_Uncorrect >> Current_Pending_Sector >> Offline_Uncorrectable Were all these values '0' ? Using truss might give a clue about the failure: # truss -o /tmp/truss.out zfs-send-commands make sure the outfile is made in a place with lots of spare space. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zy7CB7trCVTD1fEv>