Level 9 of 12 · about 3 weeks
File systems
What a file is, how directories and links work, how an ext-style file system lays out inodes, bitmaps and blocks, how blocks are allocated, how journaling and copy-on-write survive a crash, how the VFS joins many file systems, and how to find where disk space went.
Modules
Core: everyone needs it. Common: most jobs use it. Specialist: optional depth, safe to skip on a first read.
1
Files, directories and links
What a file is, how names map to inodes, and how hard and symbolic links differ
Core 7 parts · about 3 hours
2
Inodes and the on-disk layout
Superblock, bitmaps, inode table and data blocks, read straight from a real ext4 image
Core 7 parts · about 3 hours
3
Allocating blocks and free space
Contiguous, linked, indexed and extent allocation, and how free blocks are tracked
Core 7 parts · about 3 hours
4
Crash consistency and journaling
What a power cut can break, how fsck repairs it, and how a journal prevents it
Core 7 parts · about 3 hours
5
Copy-on-write and log-structured file systems
Never overwrite, always write somewhere new: batching, snapshots and the cost of cleaning
Common 7 parts · about 3 hours
6
Mounting, the VFS and special file systems
One tree from many file systems, one set of calls for all of them, and files that are not on a disk
Core 7 parts · about 3 hours
7
Case study, where did the disk space go
Why df and du disagree, and a checklist for a disk that is full with nothing in it
Common 7 parts · about 3 hours