Inodes¶
Every file on a Linux filesystem is backed by an inode — a data structure that stores metadata and block pointers. Understanding inodes explains hard links, inode exhaustion incidents, and why df can show free space while the filesystem is effectively full. This is foundational knowledge for anyone managing Linux servers.
Contents¶
Start with the primer for the core mental model, then explore pitfalls and hands-on techniques.
| # | File | What it covers |
|---|---|---|
| 1 | Primer | What inodes store, how they map to files, hard vs soft links, and filesystem allocation |
| 2 | Anti-Primer | Misconceptions about inodes, file identity, and what "deleting a file" actually means |
| 3 | Footguns & Pitfalls | Inode exhaustion, open-file-handle leaks, and cross-device link failures |
| 4 | Street Ops | Checking inode usage, finding inode-heavy directories, and recovering from exhaustion |
| 5 | Trivia & Interesting Facts | Historical design decisions and filesystem-specific inode behaviors |