<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ext4 on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ext4/</link>
    <description>Recent content in Ext4 on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ext4/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Filesystem Integrity Check Tools: fsck.ext4 vs xfs_repair vs btrfs check</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-linux-filesystem-integrity-check-fsck-xfs-repair-btrfs-guide/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-linux-filesystem-integrity-check-fsck-xfs-repair-btrfs-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Filesystem corruption is one of the scariest moments for any self-hoster. A power outage during a write, a failing SSD with silent bit flips, or a kernel panic mid-transaction can leave your filesystem in an inconsistent state. When that happens, the only thing standing between you and data loss is the filesystem check and repair tool specific to your filesystem.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
