file systems
DESCRIPTION
File Systems. Long-term Information Storage. Must store large amounts of data Information stored must survive the termination of the process using it Multiple processes must be able to access the information concurrently. File Naming. Typical file extensions. File Structure. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/1.jpg)
1
File Systems
![Page 2: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/2.jpg)
2
Long-term Information Storage
• Must store large amounts of data
• Information stored must survive the termination of the process using it
• Multiple processes must be able to access the information concurrently
![Page 3: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/3.jpg)
3
File Naming
Typical file extensions.
![Page 4: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/4.jpg)
4
File Structure
• Three kinds of files– byte sequence– record sequence– tree
![Page 5: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/5.jpg)
5
File Types
(a) An executable file (b) An archive
![Page 6: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/6.jpg)
6
File Access• Sequential access
– read all bytes/records from the beginning– cannot jump around, could rewind or back up– convenient when medium was mag tape
• Random access– bytes/records read in any order– essential for data base systems– read can be …
• move file marker (seek), then read or …
• read and then move file marker
![Page 7: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/7.jpg)
7
File Attributes
Possible file attributes
![Page 8: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/8.jpg)
8
File Operations
1. Create
2. Delete
3. Open
4. Close
5. Read
6. Write
7. Append
8. Seek
9. Get attributes
10.Set Attributes
11.Rename
![Page 9: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/9.jpg)
9
DirectoriesSingle-Level Directory Systems
• A single level directory system– contains 4 files– owned by 3 different people, A, B, and C
![Page 10: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/10.jpg)
10
Two-level Directory Systems
Letters indicate owners of the directories and files
![Page 11: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/11.jpg)
11
Hierarchical Directory Systems
A hierarchical directory system
![Page 12: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/12.jpg)
12
A UNIX directory tree
Path Names
![Page 13: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/13.jpg)
13
Directory Operations
1. Create
2. Delete
3. Opendir
4. Closedir
5. Readdir
6. Rename
7. Link
8. Unlink
![Page 14: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/14.jpg)
14
File System Implementation
A possible file system layout
![Page 15: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/15.jpg)
15
Implementing Directories (1)
(a) A simple directoryfixed size entriesdisk addresses and attributes in directory entry
(b) Directory in which each entry just refers to an i-node
![Page 16: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/16.jpg)
16
Shared Files (1)
File system containing a shared file
![Page 17: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/17.jpg)
17
Shared Files (2)
(a) Situation prior to linking
(b) After the link is created
(c)After the original owner removes the file
![Page 18: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/18.jpg)
18
File System Performance (1)
The block cache data structures
![Page 19: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/19.jpg)
19
File System Performance (2)
• I-nodes placed at the start of the disk• Disk divided into cylinder groups
– each with its own blocks and i-nodes
![Page 20: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/20.jpg)
20
Log-Structured File Systems
• With CPUs faster, memory larger– disk caches can also be larger– increasing number of read requests can come from cache– thus, most disk accesses will be writes
• LFS Strategy structures entire disk as a log– have all writes initially buffered in memory– periodically write these to the end of the disk log– when file opened, locate i-node, then find blocks
![Page 21: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/21.jpg)
21
Example File Systems CD-ROM File Systems
The ISO 9660 directory entry
![Page 22: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/22.jpg)
22
The CP/M File System (1)
Memory layout of CP/M
![Page 23: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/23.jpg)
23
The CP/M File System (2)
The CP/M directory entry format
![Page 24: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/24.jpg)
24
The MS-DOS File System (1)
The MS-DOS directory entry
![Page 25: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/25.jpg)
25
The MS-DOS File System (2)
• Maximum partition for different block sizes• The empty boxes represent forbidden combinations
![Page 26: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/26.jpg)
26
The Windows 98 File System (1)
The extended MOS-DOS directory entry used in Windows 98
Bytes
![Page 27: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/27.jpg)
27
The Windows 98 File System (2)
An entry for (part of) a long file name in Windows 98
Bytes
Checksum
![Page 28: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/28.jpg)
28
The Windows 98 File System (3)
An example of how a long name is stored in Windows 98
![Page 29: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/29.jpg)
29
The UNIX V7 File System (1)
A UNIX V7 directory entry
![Page 30: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/30.jpg)
30
The UNIX V7 File System (2)
A UNIX i-node
![Page 31: File Systems](https://reader035.vdocument.in/reader035/viewer/2022062723/56813c80550346895da621e3/html5/thumbnails/31.jpg)
31
The UNIX V7 File System (3)
The steps in looking up /usr/ast/mbox