<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ZFS on iMil.net</title>
    <link>http://imil.net/blog/tags/zfs/</link>
    <description>Recent content in ZFS on iMil.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 18 Apr 2022 17:06:48 +0200</lastBuildDate>
    <atom:link href="http://imil.net/blog/tags/zfs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating A ZPool To A Smaller Disk</title>
      <link>http://imil.net/blog/posts/2022/migrating-zpool-to-a-smaller-disk/</link>
      <pubDate>Mon, 18 Apr 2022 17:06:48 +0200</pubDate>
      <guid>http://imil.net/blog/posts/2022/migrating-zpool-to-a-smaller-disk/</guid>
      <description>&lt;p&gt;A week ago, I&amp;rsquo;ve migrated my gateway to a standalone machine running &lt;em&gt;FreeBSD&lt;/em&gt; 13.1. The whole process was certainly flawless and soon enough it was forwarding packets to and from my network.&lt;/p&gt;&#xA;&lt;p&gt;Quite happy with the result, I didn&amp;rsquo;t expect it to crash less than 2 days after its first production hour. At first I thought it could have been the temperature, the graphic card, the memory&amp;hellip; until it crashed again a couple of days after and I saw this:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Boot an Existing ZFS From a FreeBSD LiveCD</title>
      <link>http://imil.net/blog/posts/2021/boot-zfs-from-freebsd-livecd/</link>
      <pubDate>Tue, 08 Jun 2021 17:05:03 +0200</pubDate>
      <guid>http://imil.net/blog/posts/2021/boot-zfs-from-freebsd-livecd/</guid>
      <description>&lt;p&gt;Because I ran &lt;code&gt;gpart bootcode&lt;/code&gt; on the wrong partition of every replacement disk I swapped and because my motherboard is incapable of finding an &lt;em&gt;EFI&lt;/em&gt; partition, I basically bricked my &lt;em&gt;FreeBSD&lt;/em&gt; NAS / gateway.&lt;/p&gt;&#xA;&lt;p&gt;It took me a ridiculous amount of time in order to find how to boot into an existing &lt;em&gt;ZFS FreeBSD&lt;/em&gt; installation from a &lt;a href=&#34;https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/13.0/&#34;&gt;FreeBSD LiveCD&lt;/a&gt; (I used &lt;code&gt;mini-memstick&lt;/code&gt;).&lt;/p&gt;&#xA;&lt;p&gt;Finally, in a &lt;a href=&#34;https://lists.freebsd.org/pipermail/freebsd-questions/2014-November/262384.html&#34;&gt;2014 thread from the FreeBSD questions mailing list&lt;/a&gt;, someone mentioned the magic invocation, and from there I deducted the remaining parts.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Replacing a (silently) failing disk in a ZFS pool</title>
      <link>http://imil.net/blog/posts/2019/replacing-a-silently-failing-disk-in-a-zfs-pool/</link>
      <pubDate>Tue, 02 Jul 2019 17:13:31 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2019/replacing-a-silently-failing-disk-in-a-zfs-pool/</guid>
      <description>&lt;p&gt;Maybe I can&amp;rsquo;t read, but I have the feeling that official documentations explain every single corner case for a given tool, except the one you will actually need. My today&amp;rsquo;s struggle: replacing a disk within a &lt;a href=&#34;https://www.freebsd.org/doc/handbook/zfs.html&#34;&gt;FreeBSD ZFS pool&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;What? there&amp;rsquo;s a shitton of docs on this topic! Are you stupid?&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;I don&amp;rsquo;t know, maybe. Yet none covered the process in a simple, straight and complete manner. Here&amp;rsquo;s the story:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Migrate FreeBSD root on UFS to ZFS</title>
      <link>http://imil.net/blog/posts/2016/migrate-freebsd-root-on-ufs-to-zfs/</link>
      <pubDate>Thu, 28 Apr 2016 17:24:17 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2016/migrate-freebsd-root-on-ufs-to-zfs/</guid>
      <description>&lt;p&gt;At &lt;em&gt;${DAYJOB}&lt;/em&gt; I&amp;rsquo;m using a &lt;em&gt;FreeBSD&lt;/em&gt; workstation &lt;a href=&#34;http://imil.net/blog/2014/07/02/back-to-2000-2005-freebsd-desktop-2/&#34;&gt;for quite a while&lt;/a&gt;. Everything goes smoothly except for the filesystem. When I first installed it, I chose &lt;a href=&#34;https://en.wikipedia.org/wiki/Unix_File_System&#34;&gt;UFS&lt;/a&gt; because &lt;em&gt;FreeBSD&lt;/em&gt; installer said that &lt;em&gt;root-on-ZFS&lt;/em&gt; was &amp;ldquo;experimental&amp;rdquo;. I later learned that nobody uses &lt;a href=&#34;https://en.wikipedia.org/wiki/Unix_File_System&#34;&gt;UFS&lt;/a&gt; anymore and that &lt;em&gt;root-on-ZFS&lt;/em&gt; is perfectly stable. Thing is, I chose &lt;a href=&#34;https://en.wikipedia.org/wiki/Unix_File_System&#34;&gt;UFS&lt;/a&gt; and I deeply regret it. Not because of &lt;a href=&#34;https://en.wikipedia.org/wiki/ZFS&#34;&gt;ZFS&lt;/a&gt;&amp;rsquo;s features that absolutely do not matter for me on the desktop, but because &lt;strong&gt;FreeBSD&lt;/strong&gt; implementation of &lt;a href=&#34;https://en.wikipedia.org/wiki/Unix_File_System&#34;&gt;UFS&lt;/a&gt; is terribly, terribly slow when it comes to manipulate big files. When I say slow, I mean that &lt;code&gt;pkg upgrade&lt;/code&gt; tends to &lt;strong&gt;FREEZE&lt;/strong&gt; the entire machine while extracting archives. That slow. And before you ask, yes, there&amp;rsquo;s been a lot of tuning on that side.&lt;/p&gt;</description>
    </item>
    <item>
      <title>omnomnomnomnom</title>
      <link>http://imil.net/blog/posts/2010/omnomnomnomnom/</link>
      <pubDate>Sat, 10 Apr 2010 13:45:40 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2010/omnomnomnomnom/</guid>
      <description>&lt;p&gt;Au boulot, j&amp;rsquo;ai mis en place un &lt;a href=&#34;http://fr.wikipedia.org/wiki/Stockage_en_r%C3%A9seau_NAS&#34;&gt;NAS&lt;/a&gt;. À force de lire les louanges de &lt;a href=&#34;http://fr.wikipedia.org/wiki/ZFS&#34;&gt;ZFS&lt;/a&gt;, je me suis dit que c&amp;rsquo;était l&amp;rsquo;occasion idéale d&amp;rsquo;utiliser réellement ses capacités, et plus simplement comme &amp;ldquo;le filesystem de Solaris/OpenSolaris&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;Nous sommes partis de l&amp;rsquo;hypothèse suivante :&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Nous utiliserons les fonctions RAID de ZFS, et non pas le RAID5 natif fourni par le controlleur du serveur de disques; en effet, après moult lectures, il apparait que le mode &lt;em&gt;RAID-Z&lt;/em&gt; de ZFS est non seulement plus flexible, plus rapide, mais également plus sur (voir par exemple &lt;a href=&#34;http://blogs.sun.com/bonwick/entry/raid_z&#34;&gt;ici&lt;/a&gt; ou &lt;a href=&#34;http://en.wikipedia.org/wiki/Non-standard_RAID_levels#RAID-Z&#34;&gt;ici&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;li&gt;La partition de boot/root fonctionnera, elle, en mode mirror et sera disponible sur tous les disques&lt;/li&gt;&#xA;&lt;li&gt;Le reste de la place disponible formera un &lt;em&gt;pool raidz&lt;/em&gt;. Nous aurions pu choisir &lt;em&gt;raidz2&lt;/em&gt;, mais ce dernier nous aurait coûté de l&amp;rsquo;espace en moins.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Le serveur que nous utilisons pour ce &lt;em&gt;setup&lt;/em&gt; comporte une carte HP de type &lt;em&gt;Smart Array g6&lt;/em&gt;, dont le firmware ne permet pas de mode &lt;a href=&#34;http://fr.wikipedia.org/wiki/JBOD&#34;&gt;JBOD&lt;/a&gt;, aussi, chaque disque formera une unité logique RAID0.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
