ZFS, Actually Storage you can finally reason about.

Ashift

concept
depth 2/3 − deeper + surface

Disks secretly do all their work in fixed-size cells (called sectors), and ashift is ZFS's recorded guess about how big a disk's cells really are. Nearly everything in ZFS can be changed later; ashift is the exception—it's decided once, when a team of disks is created, and can never be changed ("it is set at vdev creation and it is immutable"— OpenZFS docs). The two values you'll see: ashift=9 means tiny old-style 512-byte cells; ashift=12 means the modern 4-kilobyte kind.

That's why the guides scream about one small number: it's the single decision in ZFS that is actually a foundation pour.

The failure mode: modern drives have 4K physical sectors, but many report 512 for compatibility. Trust the lie and you get ashift=9 on 4K hardware—and every sub-4K write becomes a read-modify-write cycle inside the drive, forever, invisibly, on every vdev member. The pool works; it's just permanently slower, and the only exit is destroying and rebuilding the vdev.

The practice is blunt: zpool create -o ashift=12 unless you can prove your drives are truly 512-native (almost nothing you'd buy today is). ashift=12 on a genuinely-512 drive costs a little slack space; ashift=9 on a 4K drive costs performance permanently. The asymmetry does the deciding. Check an existing pool with zdb -C tank | grep ashift—better to know than to wonder.