27 ms·
It doesn't work like you think. If you change one byte of duplicated file - the only "byte" will be changed on disk (a "byte", because, technically is not a by
by pansa777 2y ago
It doesn't work like you think.
If you change one byte of duplicated file - the only "byte" will be changed on disk (a "byte", because, technically is not a byte, but a block).
As far as I understand, it works like a reflink feature in the modern linux FSs.
If so, thats really cool, and thats also a bit better than the zfs's snapshots.
Iam newbie on macos, but it looks amazing
- jonhohle 2y agoThat’s true as long as the writing application only writes to blocks that have changed. Is a VM tool going to write blocks, or write multi-MB segments of a sparse image that can be swapped atomically? Unfortunately, once a file changes there are no APIs to check which blocks are still shared (at least there weren’t as of macOS 13).