The same bug is fixed by this patch. Your bug probably results from line 551
in dmu_traverse.c, where traverse assumes that hole birth was enabled at txg 0
if it isn't enabled, rather than at txg UINT64_MAX as it should.
This bug is present on all platforms, not just ZoL; all files in ZFS are
potentially sparse, even if you write zeroes to them, as long as you have
compression enabled (maybe even if you don't, if they're created with zfs
receive). ZFS compresses blocks filled with zeroes into holes, making the
files sparse.
---
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/37#issuecomment-158551868
_______________________________________________
developer mailing list
developer@open-zfs.org
http://lists.open-zfs.org/mailman/listinfo/developer
