Btrfs for Data Hoarders: Subvolumes, Snapshots, and When It Actually Beats ZFS

Every ZFS article on this site mentions Btrfs in passing as the “other” copy-on-write filesystem, usually in a single sentence before moving on. That’s fair when the topic is ZFS specifically, but it undersells Btrfs on its own terms. It’s a mature, in-kernel filesystem with checksummed data, instant snapshots, transparent compression, and its own answer to RAID, and for a meaningful slice of data hoarders it’s the better default, not just the fallback option you settle for when ZFS isn’t available. ...

November 20, 2026 · 6 min

ZFS Snapshots for Data Hoarders: Catching Yourself (and Ransomware) Before It Costs You the Array

Every layer of protection covered elsewhere on this site has a specific job. RAID survives a dead drive (see the RAID redundancy guide). Checksums and scrubs catch silent corruption (see bit rot and checksumming). The 3-2-1 strategy (see the backup guide) gets a copy off-site. None of them protect you from the most common actual cause of data loss in a homelab: you, or something acting with your credentials, deleting or overwriting a file that was perfectly healthy a minute ago. ...

October 15, 2026 · 7 min

ZFS Send and Receive: Replicating Your Data Hoard Without rsync

If you’re already on ZFS, whether that’s TrueNAS, a Proxmox host, or a DIY OpenZFS box, the obvious tool for moving a data hoard to a second machine is rsync. It works, but it has a cost that gets worse as the hoard grows: every run has to walk the entire directory tree, stat every file, and figure out what changed before it transfers a single byte. On a pool with a few hundred thousand media files, that walk alone can take longer than the actual transfer. ZFS has a better answer built in, and it’s been there the whole time: zfs send and zfs receive. ...

October 11, 2026 · 7 min

Proxmox Snapshots vs Backups: What Each One Actually Protects You From

Every Proxmox host ships with snapshots built in, and they’re so easy to take that it’s tempting to treat them as your backup strategy. Click “Snapshot” before a risky change, click “Rollback” if it goes wrong, done. That workflow is genuinely useful, and you should use it. It is also not a backup, and conflating the two is one of the more common ways homelab operators discover, at the worst possible moment, that they had less protection than they thought. ...

September 23, 2026 · 6 min