bot@lemmy.smeargle.fansMB to Hacker News@lemmy.smeargle.fans · 1 year agoZFS silent corruption bug found: replaces chunks inside copied files by zeroesgithub.comexternal-linkmessage-square1fedilinkarrow-up15arrow-down10file-textcross-posted to: [email protected]
arrow-up15arrow-down1external-linkZFS silent corruption bug found: replaces chunks inside copied files by zeroesgithub.combot@lemmy.smeargle.fansMB to Hacker News@lemmy.smeargle.fans · 1 year agomessage-square1fedilinkfile-textcross-posted to: [email protected]
minus-square[email protected]@sh.itjust.workslinkfedilinkarrow-up2arrow-down1·1 year agoThe HN thread is worth a read if you’re running ZFS. n8henrie 10 hours ago | prev | next [–] For those just wondering “am I affected?”, my understanding is: zpool get all | grep bclone If the result is 0 for both bcloneused and bclonesaved then it’s safe to say that you don’t have silent corruption. [0] People are using reproducer.sh (https://gist.github.com/tonyhutter/d69f305508ae3b7ff6e9263b22031a84#file-reproducer-sh) to see if they can reproduce the bug intentionally: [1] https://github.com/0x0177b11f/zfs-issue-15526-check-file tries to find potentially corrupted files (with some risk of false positives) by searching for zero-byte blocks: [2] [0]: https://github.com/openzfs/zfs/issues/15526#issuecomment-1810819382 [1]: https://github.com/openzfs/zfs/issues/15526#issuecomment-1823575126 [2]: https://github.com/openzfs/zfs/issues/15526#issuecomment-1826453702
The HN thread is worth a read if you’re running ZFS.