A Finite Inventory for the Linux Inode
The article explains why Linux systems may report 'No space left on device' despite having free disk space. This issue arises from running out of inodes, which are fixed at the time of filesystem creation. The article discusses the role of inodes in file management and common scenarios that lead to inode exhaustion.
- ▪Linux filesystems, particularly ext4, have a finite number of inodes that determine how many files can be created.
- ▪Even if a disk has free space, running out of inodes can prevent the creation of new files.
- ▪Common causes of inode exhaustion include PHP session files, proxy caches, and uncleaned build artifacts.
Opening excerpt (first ~120 words) tap to expand
linux-internals A Finite Inventory for the Linux Inode Explaining why your storage volume can report 'No space left on device' even when your disk has hundreds of gigabytes of unused capacity. Published March 27, 2026 · 10 min read I once watched a seasoned sysadmin stare at a monitor for twenty minutes, convinced the hardware was lying to him. He had a 1TB volume with roughly 400GB of free space according to every standard monitoring tool, yet every time he tried to touch a simple text file, the shell barked back: No space left on device. It’s the kind of error that makes you question your sanity, or at least your understanding of basic arithmetic.The culprit wasn't a ghost in the machine or a failing disk. It was a simple case of running out of slots in a finite inventory.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Loke.dev.
Discussion
0 commentsMore from Loke.dev
