<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OpenZFS – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/openzfs/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-GB</language><lastBuildDate>Tue, 06 Oct 2026 13:40:25 +0200</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/openzfs/index.xml" rel="self" type="application/rss+xml"/><item><title>Two Things My SSDs Were Missing: TRIM After BitLocker, and a Write Cache My HPE Server Quietly Switched Off</title><link>https://www.apt-upgrade.me/2026/10/06/two-things-my-ssds-were-missing-trim-after-bitlocker-and-a-write-cache-my-hpe-server-quietly-switched-off/</link><pubDate>Tue, 06 Oct 2026 13:40:25 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/10/06/two-things-my-ssds-were-missing-trim-after-bitlocker-and-a-write-cache-my-hpe-server-quietly-switched-off/</guid><description>&lt;p&gt;HP3, my HPE MicroServer Gen10 Plus v2, is back on Debian 13 with OpenZFS. Why it left Windows again is a story for another post. This one is about the restore afterwards, and a setting that had been hiding in plain sight for &lt;em&gt;two operating systems and two blog posts&lt;/em&gt;.&lt;/p&gt;&#10;&lt;p&gt;The plan was boring, the way restores should be: a fresh RAIDZ1 pool over the same three WD Red SA500 SSDs, per-user datasets, then about 1.7 TB copied back from a USB disk with rsync. Same workflow as always: I make the calls, my AI co-admin (Claude) runs the commands and keeps an eye on the numbers. It was the numbers that started looking wrong.&lt;/p&gt;</description></item><item><title>Second Addendum: ZED Watches My Pool’s Health, Not Its Waistline</title><link>https://www.apt-upgrade.me/2026/09/11/second-addendum-zed-watches-my-pools-health-not-its-waistline/</link><pubDate>Fri, 11 Sep 2026 15:01:46 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/09/11/second-addendum-zed-watches-my-pools-health-not-its-waistline/</guid><description>&lt;p&gt;Short one, and a direct consequence of the snapshot post. Adding daily snapshots introduced something that hadn&amp;rsquo;t existed on this NAS before: a thing that grows on its own, quietly, forever, without anybody asking it to.&#10;So I went looking for whatever would tell me when the pool started filling up. The answer was mildly embarrassing.&lt;/p&gt;&#10;&lt;h2 id="-zed-has-opinions-but-not-about-this"&gt;🔍 ZED has opinions, but not about this&lt;/h2&gt;&#10;&lt;p&gt;ZED is running. It&amp;rsquo;s configured. I fixed exactly that in the last addendum, and the fix holds:&lt;/p&gt;</description></item><item><title>Everybody Smile — We’re Taking a Snapshot! Moving From rdiff-backup to ZFS on the RAIDZ1 NAS</title><link>https://www.apt-upgrade.me/2026/09/11/everybody-smile-were-taking-a-snapshot-moving-from-rdiff-backup-to-zfs-on-the-raidz1-nas/</link><pubDate>Fri, 11 Sep 2026 13:49:58 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/09/11/everybody-smile-were-taking-a-snapshot-moving-from-rdiff-backup-to-zfs-on-the-raidz1-nas/</guid><description>&lt;p&gt;I&amp;rsquo;ve written twice about this NAS already — building it with &lt;a href="https://www.apt-upgrade.me/2026/09/01/building-a-raidz1-nas-on-debian-13-with-openzfs-datasets-compression-and-the-lies-dd-told-me/"&gt;RAIDZ1 on Debian 13&lt;/a&gt;, and then the &lt;a href="https://www.apt-upgrade.me/2026/09/02/raidz1-nas-addendum-how-scrub-and-trim-actually-get-scheduled-and-the-alert-that-wasnt/"&gt;addendum about how scrub and trim actually get scheduled&lt;/a&gt;, and the alert that wasn&amp;rsquo;t.&lt;/p&gt;&#10;&lt;p&gt;This one is about versioning. For years my answer to &amp;ldquo;how do I get yesterday&amp;rsquo;s version of this file back&amp;rdquo; has been &lt;strong&gt;rdiff-backup&lt;/strong&gt;, and it&amp;rsquo;s a genuinely good answer. It&amp;rsquo;s still installed on this box:&lt;/p&gt;&#10;&lt;pre&gt;&lt;code&gt;$ rdiff-backup --version&#10;rdiff-backup 2.2.6&#10;&lt;/code&gt;&lt;/pre&gt;&#10;&lt;p&gt;But building the pool on OpenZFS put a second mechanism on the table — one that solves the same problem from a completely different direction. So I spent an evening understanding how ZFS snapshots actually work, what they cost, and where they beat the tool I&amp;rsquo;ve been happily using. This post is that evening, including the parts I got wrong on the first attempt.&lt;/p&gt;</description></item><item><title>RAIDZ1 NAS Addendum: How Scrub and Trim Actually Get Scheduled — and the Alert That Wasn’t</title><link>https://www.apt-upgrade.me/2026/09/02/raidz1-nas-addendum-how-scrub-and-trim-actually-get-scheduled-and-the-alert-that-wasnt/</link><pubDate>Wed, 02 Sep 2026 21:11:56 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/09/02/raidz1-nas-addendum-how-scrub-and-trim-actually-get-scheduled-and-the-alert-that-wasnt/</guid><description>&lt;p&gt;A short follow-up to the &lt;a href="https://www.apt-upgrade.me/2026/09/01/building-a-raidz1-nas-on-debian-13-with-openzfs-datasets-compression-and-the-lies-dd-told-me/"&gt;RAIDZ1 NAS build&lt;/a&gt;. The cheatsheet in that post gave you &lt;code&gt;zpool scrub storage&lt;/code&gt; as a command you &lt;em&gt;can&lt;/em&gt; run. What it didn&amp;rsquo;t answer is whether anything runs it &lt;em&gt;for&lt;/em&gt; you — and, since a scrub is only useful if you actually find out when it turns something up, whether the system tells you when it does. Both questions turned out to have more interesting answers than &amp;ldquo;yes, obviously.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Building a RAIDZ1 NAS on Debian 13 with OpenZFS: Datasets, Compression, and the Lies dd Told Me</title><link>https://www.apt-upgrade.me/2026/09/01/building-a-raidz1-nas-on-debian-13-with-openzfs-datasets-compression-and-the-lies-dd-told-me/</link><pubDate>Tue, 01 Sep 2026 16:55:58 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/09/01/building-a-raidz1-nas-on-debian-13-with-openzfs-datasets-compression-and-the-lies-dd-told-me/</guid><description>&lt;p&gt;⚠️ Some commands in this post create ZFS pools or delete and overwrite data. Make a backup first, try them on a test system and adapt device names and paths to your own environment.&lt;/p&gt;&#10;&lt;h3 id="-context-retiring-the-windows-box"&gt;🪟➡️🐧 Context: retiring the Windows box&lt;/h3&gt;&#10;&lt;p&gt;Some backstory, since &amp;ldquo;why does this random Debian box suddenly have three drives and strong opinions about compression&amp;rdquo; deserves an answer. Until recently, a Windows Server handled both Active Directory and file-server/NAS duties around here — and credit where due, it did the job perfectly well. Logins worked, shares worked, nobody complained, nothing was on fire. But every time I context-switched from that box into anything DevSecOps-shaped, I felt the friction: different mental model, different tooling, different muscle memory for &amp;ldquo;okay, how do I actually check what&amp;rsquo;s going on here.&amp;rdquo; The Windows server existed purely for NAS + AD login duty, while a &lt;em&gt;separate&lt;/em&gt; box was still quietly doing all the actual Linux work — jump host duties, the odd CI-adjacent task, and lately also the thing generating this very sentence. Two servers, two operating philosophies, and a slowly growing sense that I was curating a small museum of &amp;ldquo;the way this used to be done&amp;rdquo; rather than running a coherent setup. 🏛️&#10;Sure, I could&amp;rsquo;ve reached for Proxmox and virtualised my way around the decision instead of actually making it — spin up a Windows guest, keep AD around out of habit, call it consolidation. But I&amp;rsquo;ve reached the point where I&amp;rsquo;d genuinely rather put everything on Linux, on one box, and lean into that: one toolchain, one thing to patch, one thing to monitor, instead of maintaining two entirely different worlds for the sake of a file share and a login prompt. And chasing that consolidation is exactly how I ended up back at OpenZFS — if I&amp;rsquo;m rebuilding the NAS role from scratch on Linux anyway, I want the storage layer underneath it to actually be good, not just &amp;ldquo;good enough that Explorer stops complaining.&amp;rdquo;&#10;So: I reimaged a spare box as a fresh Debian 13 (trixie) install and decided it was time to stop treating storage as an afterthought — you know, the classic &amp;ldquo;I&amp;rsquo;ll organise my files properly someday&amp;rdquo; lie we all tell ourselves. Three 2TB WD Red SA500 SSDs went in, and the goal was simple on paper: a redundant pool, compression that pays for itself, and per-user shares that don&amp;rsquo;t step on each other&amp;rsquo;s toes. OpenZFS made this genuinely pleasant — once I got past a packaging quirk, a cosmetic upstream bug that gaslit me for ten minutes, and my own deeply embarrassing first benchmark. Here&amp;rsquo;s the full walkthrough, warts included. 🐛&lt;/p&gt;</description></item><item><title>Building a Homelab NAS with OpenZFS, Samba, Jenkins &amp; GitLab — Fully Automated with Ansible</title><link>https://www.apt-upgrade.me/2026/06/29/building-a-homelab-nas-with-openzfs-samba-jenkins-gitlab-fully-automated-with-ansible/</link><pubDate>Mon, 29 Jun 2026 16:24:40 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/06/29/building-a-homelab-nas-with-openzfs-samba-jenkins-gitlab-fully-automated-with-ansible/</guid><description>&lt;p&gt;📦 What was supposed to be a quick &amp;ldquo;let me set up a NAS this weekend&amp;rdquo; turned into a week of rabbit holes, yak shaving and an unreasonable number of git commits. But hey — the homelab is better for it, and everything is now automated and documented. As usual, the full Ansible codebase lives here:&lt;/p&gt;&#10;&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://github.com/aptupgrademe/www_k3s" target="_blank" rel="noopener noreferrer"&gt;github.com/aptupgrademe/www_k3s&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;Before I get to the NAS and OpenZFS — which is the actual main event — let me quickly dump the side-quests that happened along the way. Skip to &lt;a href="#zfs"&gt;the ZFS section&lt;/a&gt; if you&amp;rsquo;re impatient. I won&amp;rsquo;t judge.&lt;/p&gt;</description></item></channel></rss>