Hacker News with Generative AI: ZFS

ZFS checksum flaw: Corruption may be left unnoticed (github.com/openzfs)
While implementing the validation and decoding of ZFS Receive Resume Tokens for a personal project, I noticed that the checksum of the tokens produced by ZFS does not match the one I computed myself using the Fletcher4 checksum algorithm. Therefore I took a deeper look into the ZFS code and noticed something unexpected:
A gotcha with importing ZFS pools and NFS exports on Linux (utoronto.ca)
Ever since its Solaris origins, ZFS has supported automatic NFS and CIFS sharing of ZFS filesystems through their 'sharenfs' and 'sharesmb' properties.
Synology DS923 vs. FreeBSD with ZFS (blogsystem5.substack.com)
My interest in storage is longstanding—I loved playing with different file systems in my early Unix days and then I worked on Google’s and Microsoft’s distributed storage solutions—and, about four years ago, I started running a home-grown NAS leveraging FreeBSD and its excellent ZFS support. I first hosted the server on a PowerMac G5 and then upgraded it to an overkill 72-core ThinkStation that I snapped second-hand for a great price.
Consider adding warnings against using ZFS native encryption (github.com/openzfs)
Among experienced zfs users and developers, it seems to be conventional wisdom that zfs native encryption is not suitable for production usage, particularly when combined with snapshotting and zfs send/recv. There is a long standing data corruption issue with many firsthand user reports:
ZFS native encryption is currently broken for encrypted backups (ycombinator.com)
There are various issues on ZFS native encryption. ZFS native encryption has been especially buggy when raw encrypted zfs snapshots are being sent or received.
Why are my ZFS disks so noisy? (allthingsopen.org)
Earlier this year, a user at Practical ZFS asked a deceptively simple question:
Troubleshooting my offline Zpool (ogselfhosting.com)
Disaster Recovery with ZFS and Zrepl (chromakode.com)