Linux File System Architecture Guide: Inodes, Types & Formats

 1. What is a Linux File System?

 A File System is the underlying data structure and indexing mechanism by which an operating system controls how data is saved, identified, isolated, and retrieved from physical storage media (such as NVMe SSDs, SATA hard drives, USB flash drives, or network shares). Without a filesystem, data stored on a storage medium would be an unorganized, monolithic stream of billions of raw binary zeroes and ones with no way to tell where one file ends and the next begins.

 Unlike Windows—which assigns individual drive letters (such as C:, D:, and E:) to partitions—Linux treats all storage devices as part of a single, unified, inverted tree structure originating from the single root directory represented by a forward slash (/).

 2. The Golden Unix Principle: "Everything is a File"

 One of the fundamental design philosophies inherited from Unix is that virtually all resources in the operating system are represented as files. This architectural elegance allows software applications to communicate with hard drives, memory, terminal screens, and network sockets using identical, standardized system calls (open(), read(), write(), and close()).

 3. Anatomy of a File System: Superblock, Inodes & Data Blocks

 When a disk partition is formatted with a filesystem (such as ext4), the operating system creates several structural regions across the storage sectors:

What Exactly is an Inode?

 An Inode (short for Index Node) is a 256-byte data structure containing all metadata about a file:

• File type (regular, directory, symlink, device)
• File size in bytes
• File permissions (read, write, execute for user/group/others)
• Owner User ID (UID) and Group ID (GID)
• Timestamps: atime (last accessed), mtime (last modified), ctime (metadata change time)
• Link counter (number of hard links referencing this inode)
• Pointers (direct, indirect, and extents) pointing to the physical data blocks storing the file contents

 4. Hard Links vs. Soft (Symbolic) Links

 Linux provides two distinct methods to reference files through multiple paths:

 5. Major Linux File System Types Compared

 6. Practical Lab: Inspecting Inodes and Managing Links

 Let us practice executing essential filesystem inspection and linking commands in the terminal:

Step 1: Inspecting File Inodes with ls -li and stat

# View files along with their unique inode numbers (first column):
ls -li /etc/passwd
# Output: 142857 -rw-r--r-- 1 root root 2842 Nov 02 08:30 /etc/passwd

# View detailed metadata structure using stat:
stat /etc/passwd
# Displays exact Inode, Device ID, Links, Access/Modify/Change timestamps, and block sizes.

Step 2: Creating and Testing Hard vs. Soft Links

# 1. Create a dummy test file:
echo "Mastering Linux File Systems" > original.txt

# 2. Create a Hard Link:
ln original.txt hardlink.txt

# 3. Create a Soft (Symbolic) Link:
ln -s original.txt softlink.txt

# 4. Inspect inodes and link counts:
ls -li original.txt hardlink.txt softlink.txt
# Notice: original.txt and hardlink.txt share the IDENTICAL inode number and have link count = 2!
# softlink.txt has a DIFFERENT inode number and points to original.txt.

# 5. Delete the original file:
rm original.txt

# 6. Test both links:
cat hardlink.txt    # Still displays "Mastering Linux File Systems"!
cat softlink.txt    # Errors out: "No such file or directory" (Broken link)

Step 3: Checking Filesystem Types and Inode Usage

# View mounted filesystems, total storage, and filesystem type:
df -Th

# Check for Inode Exhaustion (crucial troubleshooting command):
df -i
# If an inode column shows 100%, the disk CANNOT create new files even if gigabytes of free disk space remain!

 7. Student Q&A and Viva Preparation

 8. Summary & Next Steps

 You now possess a thorough technical foundation of Linux file structures, inodes, data blocks, and filesystem types. In the next tutorial, we explore the standardized layout of Linux directories in Class 23: The Filesystem Hierarchy Standard (FHS 3.0).