3 ms·
They just said copy-on-write. I'm not entirely sure about the exact interplay between shred and btrfs, but shred nominally just writes random data to the file t
by drostie 14y ago
They just said copy-on-write. I'm not entirely sure about the exact interplay between shred and btrfs, but shred nominally just writes random data to the file that was already there -- if you copy-on-write that, then you are just copying random data to a different part of the filesystem, not overwriting what's already there.
You could solve this by automatically shredding deleted stuff in the background, but it would probably kill SSDs and other storage devices which you don't want to write to too often.
- dap 14y agoI don't know how shred works, but based on what you said, it assumes knowledge of how the underlying filesystem works. If there's fault to be had (and there probably isn't), it's not ZFS's. You really consider being able to shred individual files a critical filesystem feature? Over, say, not having to configure static partition sizes, having snapshots, or being completely immune by design to large classes of data corruption (including all those that require an fsck-like tool to repair)?