Your filesystem is lying to you.
Here's something most people never think about: when you save a file on ext4 or XFS, the filesystem writes it to disk and says "done." But it never checks whether what it wrote is actually what you gave it. It just trusts the hardware.
Hardware lies. Disks develop bad sectors. Controllers have firmware bugs. Cables get loose. Cosmic rays flip bits. These aren't hypotheticals — they're Tuesday. And your filesystem has no idea it happened. Your data is silently corrupted, and you won't find out until you try to open that file six months from now.
ZFS doesn't trust hardware. Every block of data gets a cryptographic checksum. Every time ZFS reads a block, it verifies the checksum. If the data doesn't match, ZFS knows it's corrupt — and if you have a mirror or RAIDZ, it automatically fetches a good copy and fixes it. While you sleep.
The features that change everything
Checksums on Everything
Every block. Every metadata structure. Every pointer. ZFS builds a Merkle tree — the same data structure Bitcoin uses — from the bottom of your storage up to the root. If anything changes without ZFS knowing, it catches it.
Copy-on-Write
ZFS never overwrites data in place. When you modify a file, it writes the new version to a new location, then atomically updates the pointer. If power fails mid-write, you have either the old version or the new version. Never a half-written mess.
Snapshots in Milliseconds
A snapshot doesn't copy your data. It just says "remember this moment." Because ZFS never overwrites blocks, the old blocks are simply preserved. A snapshot of a 500GB filesystem takes less time than pressing Enter.
Built-in Compression
Every write is transparently compressed before hitting disk. LZ4 compression adds nearly zero CPU overhead but typically gives you 1.5–2x more usable space. You don't configure it. You don't think about it. It just works.
Self-Healing
On a mirror or RAIDZ pool, when ZFS detects a corrupt block, it doesn't just report it — it fetches the good copy from the redundant disk and overwrites the bad one. Automatically. No downtime. No intervention.
No fsck. Ever.
Traditional filesystems need to be checked after a crash. That's fsck,
and on a large filesystem, it can take hours. ZFS doesn't need fsck because its
copy-on-write design means the on-disk state is always consistent. You boot. It's fine.
The licensing "problem"
ZFS was built by Sun Microsystems under the CDDL license. Linux uses the GPL. Some lawyers say these two licenses are incompatible, which means ZFS can't be shipped inside the Linux kernel. It has to be built as a separate module.
That's it. That's the whole "problem." Not a technical problem. Not a quality problem. Not a "ZFS doesn't work on Linux" problem. A licensing paperwork problem. And because of this paperwork, most Linux distributions refuse to include ZFS out of the box, leaving users to figure it out themselves.
Let's be clear about what this means: the best filesystem in existence is kept away from the most popular operating system on Earth because of two documents written in the 1990s by people who never imagined this situation. Linux users are left with ext4 (solid, but no checksums, no snapshots, no self-healing) or btrfs (ambitious, but not ready for the trust level ZFS has earned over two decades).
kldload exists because that's ridiculous. We handle the DKMS build, the module signing, the initramfs integration, and the bootloader configuration. You get ZFS on root. Done right. You focus on your work.