← sources

ZFS or SnapRAID

source: reddit (reddit:selfhosted)published 2026-11-17 11:49ingested 2026-11-18 02:39

retained text

Looking for a sanity check before I redo my storage.  
Setup is a Proxmox box. Jellyfin runs in an LXC, and the arrs, SAB and qBit run in Docker in a Debian VM. The media gets passed into the VM with virtiofs, and the arrs hardlink from the downloads folder into Movies/TV. Right now the library is about 5.6TB on a single 14TB IronWolf Pro (ZFS), and it gets sent nightly with zfs send to a 12TB Toshiba N300 Pro as a backup. 

Works fine, but because of the backup drive I've had to cap the media at around 9TB. 

I have 20TB Exos X20 on the way, so I'll have 20/14/12 to work with. I see two ways to go:

Keep ZFS. The 20TB becomes the media drive and the 14 and 12 become backups (thinking TV on one, movies on the other, so one dead backup drive only takes out half the backup). That's about 16TB usable, I keep snapshots, and I have a real second copy.

Switch to SnapRAID + mergerfs. The 20TB becomes parity and the 14 and 12 become data drives, for about 26TB usable. One-drive fault tolerance, nightly sync, but no separate backup.

With drive prices where they are, getting \~10TB more out of the same three drives is pretty tempting. The other important stuff (VM backups, photos) is handled separately and isn't part of this.

So my questions:  
For a library that mostly just grows, is SnapRAID the obvious pick here, or am I underrating having an actual backup copy?

Has anyone run mergerfs under a virtiofs share into a VM? Any problems with hardlinks from the arrs? From what I read, I'd need a path-preserving create policy so downloads and media stay on the same disk.

Anything you'd do differently with a 20/14/12 mix?  
Appreciate any input!

document fetched 2026-11-18 00:30 · canonical https://reddit.com/r/selfhosted/comments/1xyifia/zfs_or_snapraid