File System Architecture
Every piece of data on a computer needs a home. Not just a physical location on a storage device, but a logical structure that makes that data findable, readable, and manageable.
That structure is the file system, and it is one of the most fundamental layers of any operating system.
What is a File?
At its most basic level, a file is a named container holding related information stored on a secondary storage device like a hard drive, SSD, or USB stick.
From the hardware's perspective, everything is just ones and zeros. The file is the abstraction that gives those bits meaning and a name that humans can work with. Different kinds of files have different internal structures:
- A text document is organized as a sequence of characters arranged into lines.
- A source code file is structured around functions, classes, and modules.
- A compiled binary is arranged into blocks of machine-readable instructions.
Operating systems need to understand these structures to handle them correctly. Modern systems (like Unix and Windows) keep the number of natively understood file structures minimal, leaving interpretation largely to the applications themselves.
Types of Files
- Ordinary Files: These hold the data users actually create and care about. Documents, spreadsheets, images, executables, and database files all fall here. Users can create, read, modify, and delete these freely.
- Directory Files: Rather than holding user data, these files hold metadata about other files (names, sizes, locations, permissions). They are essentially the index cards that make navigation through storage possible.
- Special Files (Device Files): These represent physical hardware components rather than stored data. A printer or a network interface can each have a corresponding special file. Character special files handle data one character at a time (keyboards), while Block special files handle data in fixed-size chunks (disk drives).
The Hierarchical File System
A file system is the organizational framework an OS uses to store, retrieve, and manage files on a storage device. Without it, a hard drive is just an undifferentiated sea of bits with no way to tell where one file ends and another begins.
File systems typically organize data hierarchically, with a "root" directory containing subdirectories, which in turn contain more subdirectories and files at various depths.
/home
│── alice
│ │── projects
│ │ │── website
│ │ │ │── index.html
│ │ │ │── style.css
│ │ │── notes.txt
│ │── music
│ │── playlist.mp3
│── bob
│ │── downloads
│ │── report.pdf
│ │── setup.exe
│── shared
│── team_doc.docx
│── budget.xlsxFile Access Methods
How an application reads data from a file depends on the access method in use.
- Sequential Access: Data is read in order from beginning to end, one record after another. You cannot jump to the middle without passing through everything before it. (e.g., Log file readers, audio/video streaming).
- Direct (Random) Access: Any record can be reached immediately by specifying its address or offset, without reading through preceding records. (e.g., A database engine looking up a specific row number).
- Indexed Sequential Access: A hybrid of the two. An index file is maintained separately, storing pointers to various positions. The system searches the index to find the pointer, then jumps directly to that location in the main file.
How Disk Space Gets Allocated
When a file is saved, the OS has to decide which physical blocks on the storage device it will occupy. Three main strategies exist:
- Contiguous Allocation: The entire file gets stored in a consecutive run of blocks on the disk. Very fast to access, but suffers heavily from External Fragmentation as files are deleted and gaps appear.
- Linked Allocation: The file's blocks are scattered randomly across the disk. Each block contains a pointer to the next block, forming a chain. This eliminates external fragmentation, but Random Access becomes extremely slow (reaching block 50 requires following 49 pointers first).
- Indexed Allocation: Each file gets a dedicated index block that stores the direct addresses of all its data blocks. This provides fast Random Access and eliminates external fragmentation, though the index block itself consumes some extra space.
Common File System Types
Different operating systems and use cases call for different file systems. Here are the five most widely encountered ones.
FAT & exFAT
FAT (File Allocation Table): The oldest mainstream file system. FAT32 caps individual file sizes at 4GB. It lacks modern features like permissions or journaling, but remains widely used on USB drives because virtually every OS can read it.
exFAT: Designed specifically for flash storage, bridging the gap between FAT32 and NTFS. It supports massive files and works natively on both Windows and macOS, making it the absolute go-to format for external USB drives.
NTFS
NTFS (New Technology File System): Microsoft's default for Windows since the late 1990s. It brings a full permission system, built-in encryption, file compression, and journaling that helps recover from crashes without corruption.
HFS+ & APFS
HFS+: Apple's old default file system, powering Macs from the late 1990s through the mid-2010s.
APFS (Apple File System): Introduced in 2017, APFS was built from scratch with SSDs and flash storage in mind. It brings features HFS+ never had: file cloning (instant copies that share blocks with the original), volume snapshots, native encryption, and space sharing between volumes.
File System Feature Comparison
| File System | Max File Size | Permissions | Journaling | Best For |
|---|---|---|---|---|
| FAT32 | 4 GB | No | No | Universal compatibility, older devices |
| NTFS | 16 TB | Yes | Yes | Windows system drives |
| exFAT | 16 EB | No | No | Cross-platform flash storage |
| HFS+ | 8 EB | Yes | Yes | Older macOS systems |
| APFS | 8 EB | Yes | No (uses COW) | Modern Apple devices and SSDs |
Summary
The file system is the invisible layer that turns raw storage into something useful. It determines how data is organized, how quickly it can be found, how resilient it is against corruption, and what security controls can be applied to it.
Choosing the right file system involves balancing compatibility, performance, feature requirements, and the type of storage hardware involved.