The Filesystem Landscape
concept"Which filesystem is best?" is the naive question, and the internet will happily fight about it forever. Actually, filesystems are tools for different jobs, and the real question is "what does each one promise?" Most of the familiar ones promise: your records will survive a crash. ZFS promises something stronger and rarer: your data will be verified, and if a copy exists, repaired—across many disks, as one system. Nothing else in wide use makes that full promise; one system (Btrfs) makes most of it. That difference, not speed or popularity, is what you're choosing when you choose ZFS.
The roster, one honest line each:
- ext4 — the Linux default. Journaled, fast, two decades of debugging. Trusts the disk completely. The right answer for most single-disk Linux machines.
- XFS — ext4's heavy-duty sibling (the default on Red Hat systems); excels at large files and parallel work. Same trust in the disk.
- NTFS — Windows' filesystem since the 90s. Journaled, capable, and not really a choice—it's what Windows is.
- APFS — Apple's modern filesystem. Shares real DNA with ZFS (copy-on-write, snapshots) but skips data checksums and multi-disk redundancy: it's the single-SSD-in-a-laptop distillation of the ideas.
- Btrfs — the closest relative: ZFS's convictions (checksums, snapshots, multi-disk pools) rebuilt inside the mainline Linux kernel. Mature for single disks and mirrors; its RAID5/6-style parity modes never became trustworthy, which is the caveat that keeps it second.
- exFAT / FAT32 — the interchange formats. No journal, no ownership, no promises; readable by everything. Perfect for a camera card, unthinkable for your archive.