Why ext4 on a single drive is the right choice for most households

Walk into r/datahoarder with a single-drive setup and you will be told to run ZFS on a mirror, or btrfs with snapshots, or at minimum a RAID 1 with weekly scrubs. The advice is correct for the threat model the people giving it are running — tens of terabytes of irreplaceable media, an ongoing acquisition habit, and an evening every quarter to maintain it. Most households are not running that threat model. For the rest of us, single-drive ext4 with an off-site copy is the defensible choice, and the noise about it being a compromise mostly comes from people whose use case is different.

What RAID actually solves

RAID protects against drive failure during operation. If a disk dies on Tuesday afternoon, the array keeps serving while you replace it. RAID does not protect against accidental deletion, ransomware, fire, theft, or the controller card failing in a way that corrupts both halves of a mirror. It also does not protect against you. The most common cause of data loss in home setups is the operator, and a mirror copies your operator-mistake to two places.

What protects against operator-mistakes, fire, theft, and ransomware is an off-site copy. That is the property you actually want. RAID is an availability feature; off-site backup is a durability feature. Households almost always want durability and almost never need RAID-level availability for personal photos.

What ZFS and btrfs add over ext4

ZFS and btrfs offer two real things ext4 does not. Checksumming detects bit-rot — the slow accumulation of silent errors in stored data — and snapshots let you roll back a folder to a previous state without keeping full duplicates. These are useful properties. They cost operational complexity, RAM, and (for ZFS especially) a mental model that takes hours to internalize.

For ten terabytes of family photos accumulated over fifteen years, the silent-bit-rot risk is real and the math says use ZFS. For a few hundred gigabytes of photos and documents on a drive that gets backed up off-site weekly, the silent-bit-rot risk is dwarfed by the everyday risks ext4 handles fine: running out of space, a power blip during a write, somebody dropping the drive. ext4 has been the default Linux filesystem since 2010. It is the most-tested storage code on the planet outside of NTFS and HFS+, and it does what it says.

The honest tradeoff

Single-drive ext4 trades acceptance of one specific risk class — this drive's individual failure — against a much simpler operating model. You accept that if the drive fails, you restore from your off-site copy and lose whatever you wrote between the last sync and the failure. You do not accept losing data permanently. That is the off-site copy's job, and the off-site copy is the thing the threat model actually demands.

The compromise people imagine you're making is between ext4 and ZFS. The compromise you are actually making is between operating-burden and operating-correctness. ZFS on a mirror buys you uptime during a drive failure but adds a tax in setup, monitoring, and replacement-disk procurement that most people pay grudgingly and many ignore until something breaks.

When you should not pick the boring path

Three real cases where ext4 on a single drive is the wrong answer. If you're running a home media server with tens of terabytes of media you actively curate, the silent-bit-rot timeline is short enough that ZFS earns its keep. If you're running anything that can't tolerate a hours-long outage during a drive replacement — a small office, a shared family server people depend on for work — you want a mirror because availability matters. If you're running multi-user services where users can write independently, you want snapshots so one user's mistake doesn't need a full restore.

Outside those cases, the boring path holds up under inspection. The first question to ask before reaching for ZFS is not “what does this offer” but “what is my threat model”. Most personal-storage threat models are dominated by off-site loss scenarios, not on-site availability scenarios. Running the right tool for your threat model is more defensible than running the fancier tool because the forum told you to.

For the higher-level framing — what threats your storage actually needs to survive, and which common setups miss them — see “The actual threat model for personal data”. On the side-by-sides: Harbor Dock vs Synology (where the filesystem and RAID conversation is most acute) and Harbor Dock vs Raspberry Pi DIY (where you'd pick your own filesystem regardless).