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.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Loke.dev |
| Canonical URL | https://loke.dev/blog/linux-inode-exhaustion-metadata-limits |
| Publication time | Mon, 25 May 2026 10:32:45 +0000 |
| Retrieval time | 2026-05-25T10:37:36.650Z |
| Last seen | 2026-05-25T10:37:36.650Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | rzatCz1h6Owv |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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
