3 ms·
>I can't have a write to one file appear in a completely different file just because they had the same contents at one point. The act of saving should destroy
by boomboomsubban 7y ago
>I can't have a write to one file appear in a completely different file just because they had the same contents at one point.
The act of saving should destroy the link, though I know that isn't always the case. Still, this is a benefit of a CoW filesystem, not offline dedupe. Permissions may be a problem, I'm not great with them.
>Those are read-only views, not real folders.
Then mount them writable,
>But for ZFS specifically you gain a lot by not using its deduplication system. It needs tons of memory and explodes files into fragments
Live deduplication is valuable in some instances, otherwise there are still offline alternatives available.
- Dylan16807 7y ago> this is a benefit of a CoW filesystem, not offline dedupe It's one method of gaining CoW. And ZFS does not support CoW between files. But whatever feature you lump it under, it's an advantage Btrfs has. > Then mount them writable, You can't.[1] And even if you could, you can't make a hard link between subvolumes. [1] You can 'clone' a snapshot to make a writable subvolume, but the original read-only snapshot can never be deleted while the clone exists, so this doesn't help you fix duplicates.