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 Special Vdev and L2ARC: Where Flash Actually Helps a Spinning-Disk Data Hoard

Every data hoarder eventually hears that you can “throw an SSD at ZFS” to speed things up, and then runs into the problem that ZFS actually has three unrelated ways to do that, with very different costs and very different payoffs. A special vdev, L2ARC, and a SLOG solve three different problems, and for a typical bulk-storage pool full of media, backups, and archives, one of them is genuinely worth doing, one is situational, and one does almost nothing for this workload no matter how fast the drive is. Mixing them up is the single easiest way to spend money on flash and get disappointed. ...

November 12, 2026 · 7 min

Proxmox Storage Replication: Near-HA Without Ceph or Shared Storage

The clustering article on this site already made the point that shared or replicated storage is the real gate on HA failover, not quorum. What it didn’t do is explain the replication half of that sentence, because it’s a separate feature with its own setup, its own limits, and its own failure modes. If you’re running a two or three node homelab cluster without Ceph and without a NAS acting as shared storage over NFS or iSCSI, Proxmox’s built-in storage replication is very likely the tool that gets you automatic failover anyway, and it’s worth understanding on its own rather than as a footnote to HA. ...

October 29, 2026 · 8 min

ZFS Deduplication: Why You Almost Never Want It Turned On (and When You Might)

If you’ve spent any time reading ZFS documentation, you’ve run across zfs set dedup=on and the promise behind it: never store the same block twice, anywhere in the pool. For a data hoarder sitting on terabytes of media, backups, and downloads, that sounds like free space. It mostly isn’t. ZFS dedup is one of the most misunderstood features in the whole stack, and the honest advice from almost everyone who has actually run it at scale is the same: leave it off unless you have a specific, measured reason not to. ...

October 23, 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

Multi-Bay DAS Enclosures: Expanding Drive Bays Without Building a Second NAS

Every data hoard eventually outgrows its case. The main server is full, the HBA’s ports are full, and the next logical move looks like building a second NAS from scratch, a second motherboard, a second CPU, a second OS to patch and monitor. Before doing that, it’s worth asking whether the actual problem is “I need more compute” or just “I need more drive bays,” because those are different problems with different, much cheaper answers. A DAS enclosure is the second answer: a box of drive bays with no brain of its own, attached to a host system that already exists. ...

October 6, 2026 · 6 min

Encrypting Your Data Hoard: LUKS vs ZFS Native Encryption vs VeraCrypt

Most data hoarding advice is about keeping data alive: redundancy, checksums, off-site copies. Almost none of it is about keeping that data private if a drive leaves your control. And drives leave your control more often than people think - a failed disk goes back to the manufacturer under warranty, a drive gets sold or handed off once you upgrade capacity, a laptop or external drive gets lost or stolen. If none of that data was encrypted, every one of those events is a potential data breach, not just an inconvenience. ...

October 3, 2026 · 7 min

Choosing SSDs for Your Homelab: Consumer vs Enterprise, and Where Endurance Actually Matters

Every homelab ends up with SSDs doing several different jobs at once: booting the hypervisor, holding VM disks, backing a ZFS special vdev or SLOG, maybe just serving as bulk fast storage for a database. Most buying advice treats this as one decision, “get an SSD, more capacity is better,” and stops there. That’s fine for a boot drive. It’s a real mistake for anything doing sustained writes, and it can quietly cost you data integrity on a ZFS log device. The differences between consumer and enterprise flash are specific and they map directly onto which job a drive should actually do. ...

September 24, 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