Bài giảng Operating system Concepts - Chapter 12: File system Implementation

Nội dung text: Bài giảng Operating system Concepts - Chapter 12: File system Implementation

1. Chapter 12: File System Implementation n File System Structure n File System Implementation n Directory Implementation n Allocation Methods n Free-Space Management n Efficiency and Performance n Recovery n Log-Structured File Systems n NFS Operating System Concepts 12.1 Silberschatz, Galvin and Gagne 2002
2. File-System Structure n File structure F Logical storage unit F Collection of related information n File system resides on secondary storage (disks). n File system organized into layers. n File control block – storage structure consisting of information about a file. Operating System Concepts 12.2 Silberschatz, Galvin and Gagne 2002
3. Layered File System Operating System Concepts 12.3 Silberschatz, Galvin and Gagne 2002
4. A Typical File Control Block Operating System Concepts 12.4 Silberschatz, Galvin and Gagne 2002
5. In-Memory File System Structures n The following figure illustrates the necessary file system structures provided by the operating systems. n Figure 12-3(a) refers to opening a file. n Figure 12-3(b) refers to reading a file. Operating System Concepts 12.5 Silberschatz, Galvin and Gagne 2002
6. In-Memory File System Structures Operating System Concepts 12.6 Silberschatz, Galvin and Gagne 2002
7. Virtual File Systems n Virtual File Systems (VFS) provide an object-oriented way of implementing file systems. n VFS allows the same system call interface (the API) to be used for different types of file systems. n The API is to the VFS interface, rather than any specific type of file system. Operating System Concepts 12.7 Silberschatz, Galvin and Gagne 2002
8. Schematic View of Virtual File System Operating System Concepts 12.8 Silberschatz, Galvin and Gagne 2002
9. Directory Implementation n Linear list of file names with pointer to the data blocks. F simple to program F time-consuming to execute n Hash Table – linear list with hash data structure. F decreases directory search time F collisions – situations where two file names hash to the same location F fixed size Operating System Concepts 12.9 Silberschatz, Galvin and Gagne 2002
10. Allocation Methods n An allocation method refers to how disk blocks are allocated for files: n Contiguous allocation n Linked allocation n Indexed allocation Operating System Concepts 12.10 Silberschatz, Galvin and Gagne 2002
11. Contiguous Allocation n Each file occupies a set of contiguous blocks on the disk. n Simple – only starting location (block #) and length (number of blocks) are required. n Random access. n Wasteful of space (dynamic storage-allocation problem). n Files cannot grow. Operating System Concepts 12.11 Silberschatz, Galvin and Gagne 2002
12. Contiguous Allocation of Disk Space Operating System Concepts 12.12 Silberschatz, Galvin and Gagne 2002
13. Extent-Based Systems n Many newer file systems (I.e. Veritas File System) use a modified contiguous allocation scheme. n Extent-based file systems allocate disk blocks in extents. n An extent is a contiguous block of disks. Extents are allocated for file allocation. A file consists of one or more extents. Operating System Concepts 12.13 Silberschatz, Galvin and Gagne 2002
14. Linked Allocation n Each file is a linked list of disk blocks: blocks may be scattered anywhere on the disk. block = pointer Operating System Concepts 12.14 Silberschatz, Galvin and Gagne 2002
15. Linked Allocation (Cont.) n Simple – need only starting address n Free-space management system – no waste of space n No random access n Mapping Q LA/511 R Block to be accessed is the Qth block in the linked chain of blocks representing the file. Displacement into block = R + 1 File-allocation table (FAT) – disk-space allocation used by MS-DOS and OS/2. Operating System Concepts 12.15 Silberschatz, Galvin and Gagne 2002
16. Linked Allocation Operating System Concepts 12.16 Silberschatz, Galvin and Gagne 2002
17. File-Allocation Table Operating System Concepts 12.17 Silberschatz, Galvin and Gagne 2002
18. Indexed Allocation n Brings all pointers together into the index block. n Logical view. index table Operating System Concepts 12.18 Silberschatz, Galvin and Gagne 2002
19. Example of Indexed Allocation Operating System Concepts 12.19 Silberschatz, Galvin and Gagne 2002
20. Indexed Allocation (Cont.) n Need index table n Random access n Dynamic access without external fragmentation, but have overhead of index block. n Mapping from logical to physical in a file of maximum size of 256K words and block size of 512 words. We need only 1 block for index table. Q LA/512 R Q = displacement into index table R = displacement into block Operating System Concepts 12.20 Silberschatz, Galvin and Gagne 2002
21. Indexed Allocation – Mapping (Cont.) n Mapping from logical to physical in a file of unbounded length (block size of 512 words). n Linked scheme – Link blocks of index table (no limit on size). Q1 LA / (512 x 511) R1 Q1 = block of index table R1 is used as follows: Q2 R1 / 512 R2 Q2 = displacement into block of index table R2 displacement into block of file: Operating System Concepts 12.21 Silberschatz, Galvin and Gagne 2002
22. Indexed Allocation – Mapping (Cont.) n Two-level index (maximum file size is 5123) Q1 LA / (512 x 512) R1 Q1 = displacement into outer-index R1 is used as follows: Q2 R1 / 512 R2 Q2 = displacement into block of index table R2 displacement into block of file: Operating System Concepts 12.22 Silberschatz, Galvin and Gagne 2002
23. Indexed Allocation – Mapping (Cont.)  outer-index index table file Operating System Concepts 12.23 Silberschatz, Galvin and Gagne 2002
24. Combined Scheme: UNIX (4K bytes per block) Operating System Concepts 12.24 Silberschatz, Galvin and Gagne 2002
25. Free-Space Management n Bit vector (n blocks) 0 1 2 n-1 0 block[i] free bit[i] = 1 block[i] occupied  Block number calculation (number of bits per word) * (number of 0-value words) + offset of first 1 bit Operating System Concepts 12.25 Silberschatz, Galvin and Gagne 2002
26. Free-Space Management (Cont.) n Bit map requires extra space. Example: block size = 212 bytes disk size = 230 bytes (1 gigabyte) n = 230/212 = 218 bits (or 32K bytes) n Easy to get contiguous files n Linked list (free list) F Cannot get contiguous space easily F No waste of space n Grouping n Counting Operating System Concepts 12.26 Silberschatz, Galvin and Gagne 2002
27. Free-Space Management (Cont.) n Need to protect: F Pointer to free list F Bit map 4 Must be kept on disk 4 Copy in memory and disk may differ. 4 Cannot allow for block[i] to have a situation where bit[i] = 1 in memory and bit[i] = 0 on disk. F Solution: 4 Set bit[i] = 1 in disk. 4 Allocate block[i] 4 Set bit[i] = 1 in memory Operating System Concepts 12.27 Silberschatz, Galvin and Gagne 2002
28. Linked Free Space List on Disk Operating System Concepts 12.28 Silberschatz, Galvin and Gagne 2002
29. Efficiency and Performance n Efficiency dependent on: F disk allocation and directory algorithms F types of data kept in file’s directory entry n Performance F disk cache – separate section of main memory for frequently used blocks F free-behind and read-ahead – techniques to optimize sequential access F improve PC performance by dedicating section of memory as virtual disk, or RAM disk. Operating System Concepts 12.29 Silberschatz, Galvin and Gagne 2002
30. Various Disk-Caching Locations Operating System Concepts 12.30 Silberschatz, Galvin and Gagne 2002
31. Page Cache n A page cache caches pages rather than disk blocks using virtual memory techniques. n Memory-mapped I/O uses a page cache. n Routine I/O through the file system uses the buffer (disk) cache. n This leads to the following figure. Operating System Concepts 12.31 Silberschatz, Galvin and Gagne 2002
32. I/O Without a Unified Buffer Cache Operating System Concepts 12.32 Silberschatz, Galvin and Gagne 2002
33. Unified Buffer Cache n A unified buffer cache uses the same page cache to cache both memory-mapped pages and ordinary file system I/O. Operating System Concepts 12.33 Silberschatz, Galvin and Gagne 2002
34. I/O Using a Unified Buffer Cache Operating System Concepts 12.34 Silberschatz, Galvin and Gagne 2002
35. Recovery n Consistency checking – compares data in directory structure with data blocks on disk, and tries to fix inconsistencies. n Use system programs to back up data from disk to another storage device (floppy disk, magnetic tape). n Recover lost file or disk by restoring data from backup. Operating System Concepts 12.35 Silberschatz, Galvin and Gagne 2002
36. Log Structured File Systems n Log structured (or journaling) file systems record each update to the file system as a transaction. n All transactions are written to a log. A transaction is considered committed once it is written to the log. However, the file system may not yet be updated. n The transactions in the log are asynchronously written to the file system. When the file system is modified, the transaction is removed from the log. n If the file system crashes, all remaining transactions in the log must still be performed. Operating System Concepts 12.36 Silberschatz, Galvin and Gagne 2002
37. The Sun Network File System (NFS) n An implementation and a specification of a software system for accessing remote files across LANs (or WANs). n The implementation is part of the Solaris and SunOS operating systems running on Sun workstations using an unreliable datagram protocol (UDP/IP protocol and Ethernet. Operating System Concepts 12.37 Silberschatz, Galvin and Gagne 2002
38. NFS (Cont.) n Interconnected workstations viewed as a set of independent machines with independent file systems, which allows sharing among these file systems in a transparent manner. F A remote directory is mounted over a local file system directory. The mounted directory looks like an integral subtree of the local file system, replacing the subtree descending from the local directory. F Specification of the remote directory for the mount operation is nontransparent; the host name of the remote directory has to be provided. Files in the remote directory can then be accessed in a transparent manner. F Subject to access-rights accreditation, potentially any file system (or directory within a file system), can be mounted remotely on top of any local directory. Operating System Concepts 12.38 Silberschatz, Galvin and Gagne 2002
39. NFS (Cont.) n NFS is designed to operate in a heterogeneous environment of different machines, operating systems, and network architectures; the NFS specifications independent of these media. n This independence is achieved through the use of RPC primitives built on top of an External Data Representation (XDR) protocol used between two implementation- independent interfaces. n The NFS specification distinguishes between the services provided by a mount mechanism and the actual remote- file-access services. Operating System Concepts 12.39 Silberschatz, Galvin and Gagne 2002
40. Three Independent File Systems Operating System Concepts 12.40 Silberschatz, Galvin and Gagne 2002
41. Mounting in NFS Mounts Cascading mounts Operating System Concepts 12.41 Silberschatz, Galvin and Gagne 2002
42. NFS Mount Protocol n Establishes initial logical connection between server and client. n Mount operation includes name of remote directory to be mounted and name of server machine storing it. F Mount request is mapped to corresponding RPC and forwarded to mount server running on server machine. F Export list – specifies local file systems that server exports for mounting, along with names of machines that are permitted to mount them. n Following a mount request that conforms to its export list, the server returns a file handle—a key for further accesses. n File handle – a file-system identifier, and an inode number to identify the mounted directory within the exported file system. n The mount operation changes only the user’s view and does not affect the server side. Operating System Concepts 12.42 Silberschatz, Galvin and Gagne 2002
43. NFS Protocol n Provides a set of remote procedure calls for remote file operations. The procedures support the following operations: F searching for a file within a directory F reading a set of directory entries F manipulating links and directories F accessing file attributes F reading and writing files n NFS servers are stateless; each request has to provide a full set of arguments. n Modified data must be committed to the server’s disk before results are returned to the client (lose advantages of caching). n The NFS protocol does not provide concurrency-control mechanisms. Operating System Concepts 12.43 Silberschatz, Galvin and Gagne 2002
44. Three Major Layers of NFS Architecture n UNIX file-system interface (based on the open, read, write, and close calls, and file descriptors). n Virtual File System (VFS) layer – distinguishes local files from remote ones, and local files are further distinguished according to their file-system types. F The VFS activates file-system-specific operations to handle local requests according to their file-system types. F Calls the NFS protocol procedures for remote requests. n NFS service layer – bottom layer of the architecture; implements the NFS protocol. Operating System Concepts 12.44 Silberschatz, Galvin and Gagne 2002
45. Schematic View of NFS Architecture Operating System Concepts 12.45 Silberschatz, Galvin and Gagne 2002
46. NFS Path-Name Translation n Performed by breaking the path into component names and performing a separate NFS lookup call for every pair of component name and directory vnode. n To make lookup faster, a directory name lookup cache on the client’s side holds the vnodes for remote directory names. Operating System Concepts 12.46 Silberschatz, Galvin and Gagne 2002
47. NFS Remote Operations n Nearly one-to-one correspondence between regular UNIX system calls and the NFS protocol RPCs (except opening and closing files). n NFS adheres to the remote-service paradigm, but employs buffering and caching techniques for the sake of performance. n File-blocks cache – when a file is opened, the kernel checks with the remote server whether to fetch or revalidate the cached attributes. Cached file blocks are used only if the corresponding cached attributes are up to date. n File-attribute cache – the attribute cache is updated whenever new attributes arrive from the server. n Clients do not free delayed-write blocks until the server confirms that the data have been written to disk. Operating System Concepts 12.47 Silberschatz, Galvin and Gagne 2002