<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NAS on Thyago Seugling</title><link>https://thyago.link/tags/nas/</link><description>Recent content in NAS on Thyago Seugling</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thyago.link/tags/nas/index.xml" rel="self" type="application/rss+xml"/><item><title>ZFS on Linux: Why I Made the Switch and Never Looked Back</title><link>https://thyago.link/blog/zfs/</link><pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate><guid>https://thyago.link/blog/zfs/</guid><description>&lt;p&gt;I lost data once. Not catastrophically — a single ext4 volume quietly developing bad sectors while I assumed everything was fine, because nothing was loudly failing. By the time I noticed, the damage was done. That experience sent me down a rabbit hole that ended at &lt;strong&gt;ZFS&lt;/strong&gt;, and I haven&amp;rsquo;t looked at another filesystem for storage since.&lt;/p&gt;
&lt;h2 id="why-zfs"&gt;Why ZFS?&lt;/h2&gt;
&lt;p&gt;Most filesystems trust that the data written to disk is the data you&amp;rsquo;ll read back. ZFS doesn&amp;rsquo;t. It checksums every block, every read, and every write. Silent data corruption — the kind that accumulates invisibly over years — is caught and, with redundancy, corrected automatically. For a home lab storing years of photos, documents, and media, this matters.&lt;/p&gt;</description></item></channel></rss>