2 ms·

https://github.com/openzfs/zfs/issues/15526#issuecomment-1810800004 https://github.com/openzfs/zfs/issues/15526#issuecomment-181... > zpool get all tank | grep

https://github.com/openzfs/zfs/issues/15526#issuecomment-1810800004 https://github.com/openzfs/zfs/issues/15526#issuecomment-181... > zpool get all tank | grep bclone > kc3000 bcloneused 442M > kc3000 bclonesaved 1.42G > kc3000 bcloneratio 4.30x > My understanding is this: If the result is 0 for both bcloneused and bclonesaved then it's safe to say that you don't have silent corruption.

keep_reading 3y ago
bclones were only one way to trigger the corruption. This is not a good way to check. It's also not worth checking for because this bug has existed for many years. Your data probably wasn't affected. None of the massive ZFS storage companies out there ran into it by now either. Your data is fine. Sleep easy.