1. CS 153 Design of Operating Systems Spring 2015 Lecture 20: File Systems

2. OS Abstractions 2 Operating System Hardware Applications CPU Disk RAM ProcessFile systemVirtual memory

3. 3 File Systems l First we’ll discuss properties of physical disks u Structure u Performance u Scheduling l Then we’ll discuss how we build file systems on them u Files u Directories u Sharing u Protection u File System Layouts u File Buffer Cache u Read Ahead

4. 4 Disks and the OS l Disks are messy physical devices: u Errors, bad blocks, missed seeks, etc. l OS’s job is to hide this mess from higher level software u Low-level device control (initiate a disk read, etc.) u Higher-level abstractions (files, databases, etc.)

5. 5 Physical Disk Structure l Disk components u Platters u Surfaces u Tracks u Sectors u Cylinders u Arm u Heads Arm Heads Platter Surface Cylinder Track Sector (512 bytes) Arm

6. 6 Disk Interaction l Specifying disk requests requires a lot of info: u Cylinder #, surface #, track #, sector #, transfer size… l Older disks required the OS to specify all of this u The OS needed to know all disk parameters l Modern disks are more complicated u Not all sectors are the same size, sectors are remapped, etc. l Current disks provide a higher-level interface (SCSI) u The disk exports its data as a logical array of blocks [0…N] »Disk maps logical blocks to cylinder/surface/track/sector u Only need to specify the logical block # to read/write u But now the disk parameters are hidden from the OS

7. 7 Disks Heterogeneity l Seagate Barracuda 3.5" (workstation) u capacity: 250 - 750 GB u rotational speed: 7,200 RPM u sequential read performance: 78 MB/s (outer) - 44 MB/s (inner) u seek time (average): 8.1 ms l Seagate Cheetah 3.5" (server) u capacity: 73 - 300 GB u rotational speed: 15,000 RPM u sequential read performance: 135 MB/s (outer) - 82 MB/s (inner) u seek time (average): 3.8 ms l Seagate Savvio 2.5" (smaller form factor) u capacity: 73 GB u rotational speed: 10,000 RPM u sequential read performance: 62 MB/s (outer) - 42 MB/s (inner) u seek time (average): 4.3 ms

8. 8 Disk Performance l What does disk performance depend upon? u Seek – moving the disk arm to the correct cylinder »Depends on how fast disk arm can move (increasing very slowly) u Rotation – waiting for the sector to rotate under the head »Depends on rotation rate of disk (increasing, but slowly) u Transfer – transferring data from surface into disk controller electronics, sending it back to the host »Depends on density (increasing quickly) l When the OS uses the disk, it tries to minimize the cost of all of these steps u Particularly seeks and rotation

9. 9 Disk Scheduling l Because seeks are so expensive (milliseconds!), OS schedules requests that are queued waiting for the disk u FCFS (do nothing) »Reasonable when load is low »Does nothing to minimize overhead of seeks u SSTF (shortest seek time first) »Minimize arm movement (seek time), maximize request rate »Favors middle blocks, potential starvation of blocks at ends u SCAN (elevator) »Service requests in one direction until done, then reverse »Long waiting times for blocks at ends u C-SCAN »Like SCAN, but only go in one direction (typewriter)

10. 10 Disk Scheduling (2) l In general, unless there are request queues, disk scheduling does not have much impact u Important for servers, less so for PCs l Modern disks often do the disk scheduling themselves u Disks know their layout better than OS, can optimize better u Ignores, undoes any scheduling done by OS

11. 11 File Systems l File systems u Implement an abstraction (files) for secondary storage u Organize files logically (directories) u Permit sharing of data between processes, people, and machines u Protect data from unwanted access (security)

12. 12 Files l A file is a sequence of bytes with some properties u Owner, last read/write time, protection, etc. l A file can also have a type u Understood by the file system »Block, character, device, portal, link, etc. u Understood by other parts of the OS or runtime libraries »Executable, dll, souce, object, text, etc. l A file’s type can be encoded in its name or contents u Windows encodes type in name ».com,.exe,.bat,.dll,.jpg, etc. u Unix encodes type in contents »Magic numbers, initial characters (e.g., #! for shell scripts)

13. 13 Basic File Operations Unix l creat(name) l open(name, how) l read(fd, buf, len) l write(fd, buf, len) l sync(fd) l seek(fd, pos) l close(fd) l unlink(name) NT l CreateFile(name, CREATE) l CreateFile(name, OPEN) l ReadFile(handle, …) l WriteFile(handle, …) l FlushFileBuffers(handle, …) l SetFilePointer(handle, …) l CloseHandle(handle, …) l DeleteFile(name) l CopyFile(name) l MoveFile(name)

14. 14 File Access Methods l Different file systems differ in the manner that data in a file can be accessed u Sequential access – read bytes one at a time, in order u Direct access – random access given block/byte number u Record access – file is array of fixed- or variable-length records, read/written sequentially or randomly by record # u Indexed access – file system contains an index to a particular field of each record in a file, reads specify a value for that field and the system finds the record via the index (DBs) l Older systems provide more complicated methods l What file access method do Unix, Windows provide?

15. 15 Directories l Directories serve two purposes u For users, they provide a structured way to organize files u For the file system, they provide a convenient naming interface that allows the implementation to separate logical file organization from physical file placement on the disk l Most file systems support multi-level directories u Naming hierarchies (/, /usr, /usr/local/, …) l Most file systems support the notion of a current directory u Relative names specified with respect to current directory u Absolute names start from the root of directory tree

16. 16 Directory Internals l A directory is a list of entries u u Name is just the name of the file or directory u Location depends upon how file is represented on disk l List is usually unordered (effectively random) u Entries usually sorted by program that reads directory l Directories typically stored in files u Only need to manage one kind of secondary storage unit

17. 17 Basic Directory Operations Unix l Directories implemented in files u Use file ops to create dirs l C runtime library provides a higher-level abstraction for reading directories u opendir(name) u readdir(DIR) u seekdir(DIR) u closedir(DIR) Windows l Explicit dir operations u CreateDirectory(name) u RemoveDirectory(name) l Very different method for reading directory entries u FindFirstFile(pattern) u FindNextFile()

18. 18 Path Name Translation l Let’s say you want to open “/one/two/three” l What does the file system do? u Open directory “/” (well known, can always find) u Search for the entry “one”, get location of “one” (in dir entry) u Open directory “one”, search for “two”, get location of “two” u Open directory “two”, search for “three”, get location of “three” u Open file “three” l Systems spend a lot of time walking directory paths u This is why open is separate from read/write u OS will cache prefix lookups for performance »/a/b, /a/bb, /a/bbb, etc., all share “/a” prefix

19. 19 File Sharing l File sharing is important for getting work done u Basis for communication between processes and users l Two key issues when sharing files u Semantics of concurrent access »What happens when one process reads while another writes? »What happens when two processes open a file for writing? u Protection

20. 20 Summary l Files u Operations, access methods l Directories u Operations, using directories to do path searches l Sharing

21. 21 Next time… l File system optimizations