ZFS, Actually Storage you can finally reason about.

RAIDZ

concept
depth 1/4 − deeper + surface

RAIDZ protects a team of disks with recovery math instead of full copies: alongside your data it stores enough extra information that if a disk dies, everything on it can be recomputed from the survivors. RAIDZ1 survives one dead disk, RAIDZ2 two, RAIDZ3 three—and you keep much more usable space than mirrors give you.

Two things the space math hides. First, the good news: ZFS fixed the famous flaw of older systems built this way (a crash at the wrong instant could silently corrupt them—the "write hole"; ZFS's never-overwrite habit makes it impossible). Second, the catch that decides real setups: a RAIDZ team, no matter how many disks are in it, handles scattered small requests at roughly the pace of a single disk—because every request needs the whole team. Wonderful for big libraries read start-to-finish; wrong for virtual machines and databases.