How APFS containers and volumes work. What hard links, clones and sparse files are, and when they break down.
clone
You’re in control of a traditional file system, but with snapshots, clones, sparse files and other volumes sharing free space, APFS isn’t as simple.
Copies, clones and backups are three different things. Here their differences are explained with examples from APFS and modern macOS.
Dragging a file to copy/move it from one location to another used to be simple. Now it’s complicated by iCloud, dropbox behaviour in AirDrop and Universal Control, and more.
Confused by this on APFS? So you should be, as it’s complicated by features like snapshots, sparse files, and the file system itself. There’s no single figure.
Tired of HFS+? Disenchanted by APFS? Why not copy or back up to a different file system? Here are crocodiles waiting to bite you.
M1 Macs are different, as they always start booting from their internal SSD. Basic configurations are simple, reliable with well-established disaster recovery methods.
A lot of what Time Machine does when making backups to an APFS volume remains a mystery. So far we don’t understand the magic used by Apple.
Track down all those duplicated files, and you could save yourself loads of disk space. Rather, you used to be able to. Why this doesn’t work so well now.
For some, inability to clone to the internal SSD of an M1 Mac seems disastrous. In reality, it could achieve little, and there are better solutions.
The Eclectic Light Company 