To me it does feel like this has been on HN a bit more than other filesystem corruption bugs. This bug can basically only be triggered by using lseek to search

To me it does feel like this has been on HN a bit more than other filesystem corruption bugs. This bug can basically only be triggered by using lseek to search for a hole. Ext4 has a very similar bug, but that requires enabling inline_data (and possibly a non-default blocksize, but that doesn't always seem to be the case): https://forums.gentoo.org/viewtopic-t-1166006.html https://forums.gentoo.org/viewtopic-t-1166006.html I don't think I ever heard about this, apart from in the context of the ZFS bug. And although inline_data is niche, ext4 as a whole I would argue is not. Actually lseek seems to have been broken on most filesystems at some point: https://bugs.gentoo.org/891125 https://bugs.gentoo.org/891125 https://github.com/gluster/glusterfs/issues/894 https://github.com/gluster/glusterfs/issues/894 And apparently apart from modern coreutils using that, it is mostly gentoo users hitting the bugs in lseek.