<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Zfs on Besterry — Linux &amp; DevOps Notes</title><link>https://besterry.com/tags/zfs/</link><description>Recent content in Zfs on Besterry — Linux &amp; DevOps Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Sep 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://besterry.com/tags/zfs/index.xml" rel="self" type="application/rss+xml"/><item><title>ZFS on Linux: Six Months of Production Use</title><link>https://besterry.com/posts/zfs-on-linux/</link><pubDate>Mon, 02 Sep 2024 00:00:00 +0000</pubDate><guid>https://besterry.com/posts/zfs-on-linux/</guid><description>&lt;p&gt;Migrated our build server array from ext4+mdadm to ZFS on Linux six months ago. Here&amp;rsquo;s what I learned.&lt;/p&gt;
&lt;h2 id="why-zfs"&gt;Why ZFS&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Checksumming catches silent data corruption (we found 14 affected files on the old array)&lt;/li&gt;
&lt;li&gt;Snapshots are cheap and instant (100ms for a 10TB dataset)&lt;/li&gt;
&lt;li&gt;Compression often makes things faster — less I/O, more CPU&lt;/li&gt;
&lt;li&gt;Send/receive for efficient replication&lt;/li&gt;
&lt;li&gt;No separate mdadm/LVM layer to debug&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="pool-design"&gt;Pool design&lt;/h2&gt;
&lt;p&gt;For the build server, 6 x 4TB NVMe in RAIDZ2:&lt;/p&gt;</description></item></channel></rss>