1. 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.

2. 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.

3. Disk Architecture Sector Track Platter Arm Block: 4kb Read/write head

4. Interleaving 1:1 interleave 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Delay, interleave factor, between each block due to the overhead of the communication between the disk controller and the device driver

5. Interleaving 1:3 interleave 1 2 34 5 6 78 9 10 11 12 13 14 15 16

6. Storing a File 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 First 4K Second 4K Last 1K

7. Inodes—Index 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

8. Inodes—Index 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

9. Every file has an inode 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Block map Inode 0 1 2 3 7 2 14

10. 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. Direct block pointers Indirect pointer Disk blocks Inode

11. Direct block pointers Indirect pointer Disk blocks Inode Double indirect pointer

12. 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.

13. File System Layout Boot block Super block Inode 1…40 Inode 41..80 User block Logical disk layout Physical disk layout

14. 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 Free Used Free Used Free Disk blocks 101101 Bitmap

15. Directories Inode number 2 contains the location of the block possessing the root directory. (inode number 1 for bad blocks) /2/2 bin 3 ls 5 cp 7 usr 4 Test.c 6. 2.. 2 bin 3 usr 4 labelInode # Hard Link

16. Mounting File Systems The mount utility allows a superuser to splice the root directory of a file system into the existing directory hierarchy. / bin usr mnt / tmp1 tmp2 / bin usr mnt tmp1tmp2 $ mount /dev/flp /mnt $ unmount /dev/flp or $unmount /mnt