It looks like the source of the bug is identified and fixed.
https://github.com/openzfs/zfs/pull/15579/commits/679738cc408d575289af2e31cdb1db9e311f0adf
[2.2] dnode_is_dirty: check dnode and its data for dirtiness #15579
modinfo zfs | grep version
To quickly get the version installed.
zfs --version also does the trick.
That did not work for me on ubuntu, but did on my debian/proxmox distribution
proxmox:
zfs-0.8.3-pve1
zfs-kmod-0.8.3-pve1
ubuntu:
version: 0.6.5.6-0ubuntu26
srcversion: 0968F94158D646E259D86B5
vermagic: 4.4.0-142-generic SMP mod_unload modversions retpoline
looks like im using an ancient version and am ok?
I also use a version close to that, 0.something. See absolutely no reason to upgrade. It just works. It’s the version that has the fast scrub already.
This is why you ALWAYS need INDEPENDENT backups. You can think all day long about detecting bitrot, and how well you’re protected against X drive failures but then something comes from the side and messes up your data in a different way than you’ve foreseen.
Wait. Are you trying to say that raid is not a backup?