inode
The record a filesystem keeps for each file, holding its owner, mode, size, timestamps, link count and the location of its data blocks, but not its name.
In more detail
Names live in directories, which map each name to an inode number; the inode is the file object itself. Several names can point at the same inode, which is what a hard link is. A filesystem creates a fixed or limited number of inodes, so it can run out of them even while free space remains.
Example
ls -i shows inode numbers, and stat shows an inode's link count.Related terms
- hard link — An additional directory entry that points to an existing inode, so one file has two or more equal names.
- directory entry — One line in a directory's table that maps a file name to an inode number.
- link count — The number stored in an inode that says how many directory entries point to it.
- data block — A fixed-size chunk of disk space, often 4 kilobytes, that a filesystem uses to store a file's contents.
- inode exhaustion — A filesystem running out of inodes, so no new files can be created even though free space remains.
Taught in
- Inodes, Hard Links And What rm Removes — Linux Fundamentals & Systems Administration
- Running Out Of Space: df, du And Inodes — Linux Fundamentals & Systems Administration
- Which RAID, Which File System? Disks That Fail And Inodes That Run Out — CompTIA Linux+ (XK0-006) Exam Prep
- No Space Left, Says The Disk With Room To Spare: Inodes, Held Files, Corruption And Repair — CompTIA Linux+ (XK0-006) Exam Prep
- Ninety Minutes, Five Domains: The Full Mock And The Week Before The Exam — CompTIA Linux+ (XK0-006) Exam Prep