FirstHack Learn
Log in Sign up free
Lessons in this course 0/6 All courses Operating Systems

CSE

Progress0 / 6 lessons
  1. 1. What an OS actually does, and what a system call is
  2. 2. Processes vs threads, with a fork() example
  3. 3. CPU scheduling with worked FCFS, SJF and Round Robin numbers
  4. 4. Deadlock: the four conditions and how to break them
  5. 5. Memory: paging, virtual memory and page faults
  6. 6. File systems and how a file is really stored

Courses › Operating Systems

File systems and how a file is really stored

Inodes, block pointers, directories as tables, and why deleting a file does not erase it.

12 min read · Lesson 6 of 6 · Pro

A disk knows nothing about files

A disk offers numbered blocks, typically 4096 bytes each. Read block 91,447. Write block 91,448. That is the entire interface. There are no names, no folders, no sizes.

A file system is the data structure that turns that flat array of numbered blocks into files and directories. On Linux that is usually ext4; on Windows NTFS; on a pen drive, FAT32 or exFAT.

The inode holds everything except the name

In Unix file systems, each file has an inode — a fixed-size record holding the file's metadata:

The rest of this lesson is Pro

The free lessons of Operating Systems finish what they start — read those first if you have not. This one goes further, and it is part of the paid half.

A pass opens the paid lessons of every course, the mock test papers and the company-wise series. It ends on its own date; nothing renews by itself.

Get a pass — from ₹29 for 7 days

Already bought one? Log in.