Storage & backups
Should I use ZFS with only 2-4 drives?
Should I use ZFS on a home NAS if I only have 2-4 drives?
Short answer
Should I use ZFS on a home NAS if I only have 2-4 drives?
Yes, ZFS is worth it even at two to four drives — the data-integrity checking and instant snapshots are valuable at any size, not just on big arrays. The one adjustment for a small setup: skip RAIDZ and use mirrored pairs instead. Mirrors are simpler, rebuild faster and safer, and let you grow the pool two drives at a time, which suits how home NASes actually expand.
ZFS is a filesystem that also manages your disks. Beyond storing files, it checksums everything it writes and verifies it on read — so it detects and, with redundancy, repairs silent corruption that ordinary filesystems never notice — and it takes near-instant, space-efficient snapshots you can roll back to. A "mirror" is two drives holding identical copies; "RAIDZ" is ZFS's parity-based mode for larger arrays.
- Every readZFS verifies data against a checksum (catches bit-rot)
- Secondsto take a snapshot you can roll back to
- 2 drivesthe increment mirrors let you grow a pool byvs replacing whole RAIDZ vdevs
The benefits don’t scale down away
The instinct to think ZFS is a “big array” thing is understandable — that’s where you hear about it — but the two features that make it special are exactly as useful on a small NAS. Checksumming means ZFS notices when a bit silently flips on a disk (which does happen, quietly, on ordinary filesystems that never check), and with a mirror it repairs it from the good copy. Snapshots mean you can freeze the state of your data in seconds and roll back a bad change or an “oops I overwrote that.” Neither of those needs a dozen drives to matter.
| Factor | Mirrors | RAIDZ |
|---|---|---|
| Best drive count | 2, 4 (in pairs) | 4+ ideally |
| Grow the pool by | Adding a pair | Replacing a whole vdev |
| Rebuild after failure | Fast, low stress | Slower, more strain |
| Usable space | Half | More efficient at scale |
People assume ZFS is only for big arrays, but the bit-rot protection and snapshots are worth it even with a couple of drives. At that scale I run mirrors, not RAIDZ — simpler to grow, quicker to heal.
Common questions
Isn't ZFS overkill for a small NAS?
The heavy reputation comes from big deployments, but the two features that matter most — checksumming that catches silent corruption, and cheap snapshots — help just as much with two drives as with twenty. You don't need a huge array to benefit; you need data you'd rather not see quietly rot.
Why mirrors instead of RAIDZ with few drives?
Mirrors let you add capacity a pair at a time and rebuild quickly and safely when a disk dies. RAIDZ is more space-efficient but wants more drives to make sense and is harder to expand — you generally replace an entire group. For a home NAS that grows gradually, mirrors fit the way you actually buy disks.
Does ZFS need lots of RAM?
The 'ZFS needs enormous RAM' idea is overstated for home use. It happily uses spare RAM as cache and gives it back under pressure. A few gigabytes is fine for a small NAS; you only chase big RAM figures if you enable deduplication, which most home users should leave off.