<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Truenas - vo.rs</title><link>https://vo.rs/tags/truenas/</link><description>Latest from the Truenas desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 16 Jan 2024 08:15:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/truenas/" rel="self" type="application/rss+xml"/><item><title>TrueNAS Scale: When Your ZFS Pool Deserves Its Own Box</title><link>https://vo.rs/story/truenas-scale-when-your-zfs-pool-deserves-its-own-box/</link><description>&lt;p&gt;I ran ZFS on a general-purpose Debian box for years, hand-rolling &lt;code&gt;zpool&lt;/code&gt; commands, writing my own snapshot cron jobs, and maintaining a Samba config by hand. It worked, and I learned a great deal doing it. Then one day I needed to rebuild that box for an unrelated reason, spent an evening reconstructing the exact dataset layout, ACLs, and share config from memory and shell history, and asked myself why I was doing storage administration as a hobby rather than as infrastructure. That&amp;rsquo;s the honest answer to &amp;ldquo;why TrueNAS Scale&amp;rdquo;: at some point your storage box graduates from a project you tinker with into a thing you simply need to work, and an appliance that tracks its own configuration earns its keep at exactly that point. Roll-your-own ZFS taught me most of what I know about vdevs, ARC sizing, and send streams, and I&amp;rsquo;d still recommend the exercise to anyone who wants to actually understand the filesystem rather than click through a wizard. It&amp;rsquo;s just that understanding and daily operation are different goals, and conflating them is how you end up doing archaeology on your own shell history at 11pm.&lt;/p&gt;</description><pubDate>Tue, 16 Jan 2024 08:15:00 +0000</pubDate></item></channel></rss>