File Systems for Operating Systemss
File Systems organise data on persistent storage into files and directories. Structures such as inodes, bitmaps and data blocks track what is where, and the OS caches blocks in memory. Journaling or copy-on-write keeps the structure consistent after a crash, which is the main reliability challenge.
Stage: Persistence · Part of the Operating Systems roadmap · Last reviewed 19 November 2026
What to learn in File Systems
- Read an inode to find the data blocks of a file
- Explain the difference between hard links and symbolic links
- Trace the disk operations needed to create a new file
- Describe how journaling recovers a file system after a crash
- Reason about fragmentation and how block allocation affects speed
File Systems interview questions
What information does an inode store?
An inode holds a file's metadata: type, size, owner, permissions, timestamps, link count and pointers to its data blocks. It does not store the file name, which lives in the directory entry that maps a name to an inode number.
How does journaling protect a file system from crashes?
Before changing structures in place, the file system writes a description of the update to a log. After a crash it replays or discards complete log entries, so metadata is not left half-updated and a full consistency scan is avoided.
Where File Systems fits in the Operating Systems roadmap
File Systems belongs to the Persistence stage (advanced level). Storage and file systems.
Other units in this stage
Back to the full Operating Systems roadmap