ZFS, Actually Storage you can finally reason about.

Copy-on-Write

concept
depth 1/4 − deeper + surface

When an ordinary system saves a change, it writes the new version on top of the old one, right where it sat. That's the obvious approach, and it carries a hidden bet: that nothing goes wrong mid-write. Lose power at the wrong instant and the old version is half-destroyed while the new one is half-written—the ugly middle that older systems needed repair tools for.

Copy-on-write is ZFS's refusal to ever make that bet: existing data is never written over. Ever. When you "change" a file, ZFS writes the new version onto fresh, empty space, and then—in one clean, instant switch— makes it the official one. So at every moment, what's on disk is some complete, correct state. A change either fully happened or never happened; there is nothing half-done to repair, which is why no repair pass exists.