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

NFS, iSCSI, and SMB as Proxmox Storage Backends: What Each One Actually Gets You

Most homelab Proxmox boxes start with everything on local disk, and that’s fine right up until there’s a second box, or a NAS already doing the storage job sitting idle on the network. Proxmox can mount that NAS directly as a storage backend through Datacenter > Storage > Add, with no Ceph cluster and no replication job required. The catch is that NFS, iSCSI, and SMB aren’t interchangeable once they’re wired in. Each one supports a different subset of content types, behaves differently under a live VM, and fails in a different way when the network hiccups. Picking the wrong one for the job looks fine on day one and turns into a surprise the first time something tries to snapshot a VM or the NAS reboots mid-write. ...

November 14, 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

Recovering Data from a Dying Drive: ddrescue, Imaging, and What Not to Do

Every other article in this pillar assumes the drive is healthy. Burn-in testing catches problems before a drive ever holds data, and SMART monitoring catches the warning signs during normal service life. This one is about the moment after that, when a drive is already failing and you need to get the data off it, now, with as little further damage as possible. The single biggest mistake people make here is treating a dying drive like a normal one. They try to copy files off it, or run chkdsk, or re-run a SMART self-test “to see how bad it is.” Every one of those actions reads from a drive that’s already struggling to read reliably, and every extra read is a chance to turn a partially failing drive into a completely dead one. The right first move is almost always the opposite of instinct: stop touching the drive directly, and image it instead. ...

November 4, 2026 · 8 min

Spinning Down Hard Drives to Save Power: When It Helps and When It Just Wears Them Out

A data hoard with a dozen or more drives spends most of its life mostly idle. Only a fraction of that storage gets touched on any given day, so spinning the rest down to save power looks like an obvious win: a spinning 3.5" drive pulls somewhere around 5-9 watts at idle, versus close to nothing once it’s parked. Multiply that across fifteen or twenty drives and the number looks worth chasing. ...

October 27, 2026 · 7 min

PCIe Bifurcation and M.2 Expansion Cards: Getting More NVMe Slots Out of a Consumer Motherboard

The CPU and motherboard article on this site already covers how PCIe lane budgets get tight on a consumer platform once a GPU, an HBA, and a NIC are all fighting for slots. This piece is about the thing people reach for once that budget is spent: PCIe expansion cards that turn a single slot into multiple M.2 NVMe slots. Some of these cards work in any PCIe slot on any board. Others need a specific motherboard feature called bifurcation, and buying the wrong card for your board is a common, entirely avoidable way to end up with an expensive piece of plastic that Windows or Linux only sees one drive on. ...

October 26, 2026 · 7 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

SMART Monitoring and Drive Health Alerts: Catching a Dying Drive Before It Takes Data With It

Burn-in testing catches a bad drive before it ever holds data. Bit rot scrubbing catches silent corruption on drives that are otherwise working fine. Neither one watches a healthy drive for the slow, specific warning signs that show up months or years into its working life, the gradually climbing error counts that mean a drive is dying, not corrupted or defective out of the box. That’s a separate job: ongoing SMART monitoring with an actual alert attached to it, not a dashboard you remember to check every few months. ...

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