<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Filesystem on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/filesystem/</link>
    <description>Recent content in Filesystem on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 09:17:03 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/filesystem/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When /usr Shows 100 % Used but df Says Space Is Fine: Spotting Inode Exhaustion</title>
      <link>https://linuxeries.org/post/2026-10-08-when-usr-shows-100-used-but-df-says-space-is-/</link>
      <pubDate>Thu, 08 Oct 2026 09:17:03 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-10-08-when-usr-shows-100-used-but-df-says-space-is-/</guid>
      <description>&lt;h2 id=&#34;why-inode-exhaustion-happens&#34;&gt;Why Inode Exhaustion Happens&lt;/h2&gt;&#xA;&lt;p&gt;On a busy server you’ll often see &lt;code&gt;df&lt;/code&gt; still showing plenty of space, but &lt;code&gt;df -i&lt;/code&gt; screaming 100 % inode usage on a mount like &lt;code&gt;/usr&lt;/code&gt;. The kernel will happily refuse to create any more files, even though there’s room on disk. The culprit is usually a deluge of tiny files—think logs, temp data, or a mis‑configured service that never cleans up.&lt;/p&gt;&#xA;&lt;h3 id=&#34;spotting-the-problem-quickly&#34;&gt;Spotting the Problem Quickly&lt;/h3&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;c1&#34;&gt;# Space vs. inodes&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;df -h /usr&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;df -i /usr&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If the first command reports 20 GB free but the second is 100 % used, you’ve hit an inode shortage. Now find the directory that’s eating them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
