ZFS, Actually Storage you can finally reason about.

The Free-Space Discipline

concept
depth 2/3 − deeper + surface

Intuition says a nearly-full disk is just a disk with less room—how full it is and how fast it is are separate questions. On ordinary systems that's mostly true. Actually, because ZFS never writes over existing data, every change needs fresh, empty space to land on—even "overwrites," even deletions. A full pool forces ZFS to hunt for scraps of room; new data gets shredded into whatever gaps exist; and the pool slows down in a way that doesn't fully recover when you free space later, because the scattering already happened.

Empty space isn't spare room. It's the workshop floor every change is made on.

Operating numbers, honestly labeled as heuristics: keep general-purpose pools below ~80–85%; performance-sensitive pools (VMs, databases) appreciate more slack. Past ~90% the allocator visibly changes character; at ~100%, deletion itself gets weird—freeing space needs CoW writes too (snapshot destruction is the usual escape because it frees without writing... unless snapshots are exactly what's pinning everything—see Snapshots and Disappearing Space).

Watch two numbers: zpool list for CAP and FRAG. FRAG measures free-space fragmentation (how shredded the remaining room is), not file fragmentation—a high-FRAG, high-CAP pool is one whose future writes are already compromised. The honest fixes are the blunt ones: grow the pool (add a vdev), or want less (retention policy, quotas so one dataset can't eat the floor).