Stop staring at a frozen cursor when you run out of inodes
Disk & Filesystem Management (Du/Df/Lsblk/Fstrim)
Stop staring at a frozen cursor when you run out of inodes
🧩 The Challenge
You ever have a server that shows plenty of free space on df, yet every single app on the box is throwing I/O errors like it’s the end of the world? I spent an entire morning chasing ghost processes before realizing the filesystem had simply run out of inodes.
💡 The Fix
Use a specific df flag to check the actual inode count instead of just the block-level storage usage. It’s the only way to catch those hidden piles of tiny temporary files.
df -i
⚙️ Why It Works
Running this command forces the system to show you how many file entries are left on each partition, which usually exposes the culprit when you’ve hit the limit despite having gigabytes of “free” space.
🚀 Pro-Tip: If you actually hit this limit, find the folder causing the mess with find . -printf ‘%h\n’ | sort | uniq -c | sort -nr | head to see which directory is hoarding the most files.
Linux Tips & Tricks | © ngelinux.com | 8/21/2026
