<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Filesystems on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/filesystems/</link>
    <description>Recent content in Filesystems on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/filesystems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Zoned Storage in 2026: zonefs vs f2fs Zoned Mode vs btrfs — Which One Actually Works?</title>
      <link>https://www.pistack.xyz/posts/2026-11-17-zoned-storage-zonefs-f2fs-btrfs-zns-guide/</link>
      <pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-17-zoned-storage-zonefs-f2fs-btrfs-zns-guide/</guid>
      <description>&lt;p&gt;You bought a ZNS SSD — or you are about to — and then you discovered the fine print: &lt;strong&gt;every zone must be written sequentially, from the first block to the last, or the write fails outright&lt;/strong&gt;. No random overwrites, no in-place updates, no &amp;ldquo;just rsync your old data over.&amp;rdquo; That single constraint invalidates most of the storage stack you have been running for fifteen years, and it is the reason so many teams plug a ZNS drive into a server, see it in &lt;code&gt;lsblk&lt;/code&gt;, and then quietly move it to the &amp;ldquo;shelf&amp;rdquo; pile.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
