I know it's already integrated but the original description was about `zeroing` out the unused blocks and the implementation actually writes `0xdeadbeef` which makes it less useful for me in the case where I want to zero the blocks prior to doing a hole-punch on a sparse VM disk (and I appreciate that is the opposite to the original intention of this change).
Any reason why it is writing deadbeef instead of zeros? I see that the tests explicitly set the pattern to deadbeef for the duration of the test. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/586#issuecomment-384577160 ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/discussions/T6777d2c2033b2134-M11813122cb9d378c5cba3ffb Delivery options: https://openzfs.topicbox.com/groups
