Scribd
Upload
46 views

The File System: Files - Long-Term Storage RAM - Short-Term Storage

The file system stores files in a hierarchy of directories and uses inodes to store metadata about each file such as its type, permissions, and locations of data blocks. Inodes contain direct and indirect block pointers to address file data blocks, both on the initial disk and additional blocks for large files. The file system layout includes a boot block, superblock containing metadata about the entire file system, an inode list, and user data blocks. Directories are regular files containing links to other files' inodes. File systems can be mounted and unmounted at different points in the overall directory structure.

Uploaded by

Abhimanyu Raj
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
46 views

The File System: Files - Long-Term Storage RAM - Short-Term Storage

The file system stores files in a hierarchy of directories and uses inodes to store metadata about each file such as its type, permissions, and locations of data blocks. Inodes contain direct and indirect block pointers to address file data blocks, both on the initial disk and additional blocks for large files. The file system layout includes a boot block, superblock containing metadata about the entire file system, an inode list, and user data blocks. Directories are regular files containing links to other files' inodes. File systems can be mounted and unmounted at different points in the overall directory structure.

Uploaded by

Abhimanyu Raj
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 16

THE FILE SYSTEM

Files -------- long-term storage RAM --------- short-term storage

Programs, data, and text are all stored in files, which is stored on hard disk and other media, such as tape and floppy disk.

THE FILE SYSTEM


UNIX files are organized by a hierarchy of labels ---- directory structure

Three kinds: + Regular files, containing a sequence of bytes that generally corresponds to code or data. Referenced via the standard I/O system calls. + Directory files, a special format and forming the backbone of the file system. Referenced only via directory-specific system calls. + Special files, correspond to peripherals such as printers and disks, and interprocess communication mechanisms, such as pipes and sockets. Referenced via the standard I/O system calls.

Disk Architecture
Sector Platter

Track Arm

Block: 4kb

Read/write head

Interleaving
1:1 interleave
8 16 7

1 9 10
2

15

14 13 5 12 4

11

Delay, interleave factor, between each block due to the overhead of the communication between the disk controller and the device driver

Interleaving
1:3 interleave
6 14 3 11

1 9 12
4

16 8 5 13 10 2

15 7

Storing a File
First 4K

Second 4K Last 1K

8 16 15

1 9
10 2

14 13 5 12 4

11

InodesIndex node
To store information about each file + the type of the file: regular, directory, block special, character special, etc. + file permissions + the owner and group IDs + a hard link count + the last modification time and last access time + the location of the blocks if the file is a regular or directory file + the major and minor device numbers if the file is a special file + the value of the symbolic link if the file is a symbolic link

In other words, it contains all of the information when you perform an ls -l, except for the filename

InodesIndex node
Every inode in a particular file system is allocated a unique inode number.

Every file has exactly one inode.


All the inodes associated with the files on a disk are stored in a special area at the start of the disk called the inode list

Inode Block map 0 1 2 3 7 2 14

Every file has an inode

8 16 7 15

1 9 10 2

14 13

11

12 4

The Block Map


Inode only stores the first 10 blocks of a file. (most UNIX files are less than 40K) An indirect access scheme is used for addressing larger files.
Inode

Direct block pointers

Indirect pointer

Disk blocks

Inode

Direct block pointers

Indirect pointer

Disk blocks Double indirect pointer

File System Layout


boot block: first logical block of a disk, containing some executable code that is used when UNIX is first activated. super block: second logical block of a disk, containing information concerning the disk itself. inode list: following fixed-size set of blocks, holding all of the inodes associated with the files on the disk.

File System Layout


Logical disk layout Boot block Super block Inode 140

Inode 41..80

Physical disk layout User block User block User block

The Superblock
It contains information pertaining to the entire file system.
+ the total number of blocks in the file system + the number of inodes in the inode free list + the size of a block in bytes + the number of free blocks + the number of used blocks

Disk blocks
Free
Used

Bitmap
1 0 1 1 0 1

Free
Free Used Free

Directories
Inode number 2 contains the location of the block possessing the root directory. (inode number 1 for bad blocks)
label /2 Inode #

.
.. bin

2
2 3 4

bin3

usr4

usr Hard Link

ls5

cp7

Test.c6

Mounting File Systems


The mount utility allows a superuser to splice the root directory of a file system into the existing directory hierarchy. $ mount /dev/flp /mnt $ unmount /dev/flp
/

or
/

$unmount /mnt
/

bin bin mnt usr tmp1 tmp2 tmp1

mnt

usr

tmp2

You might also like