Top Banner
Chapter 10: File-System Chapter 10: File-System Interface Interface
30
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Ch10

Chapter 10: File-System InterfaceChapter 10: File-System Interface

Page 2: Ch10

Files Files

Page 3: Ch10

10.3 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

File Concept & Structure File Concept & Structure

Contiguous persistent logical address space, can be storing data or programs

File Structure: None - sequence of words, bytes Simple record structure

Lines Fixed length Variable length

Complex Structures Formatted document Relocatable load file

Can simulate last two with first method by inserting appropriate control characters

Who decides: Operating system Program

Page 4: Ch10

10.4 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

File AttributesFile Attributes

Name – only information kept in human-readable form

Identifier – unique tag (number) identifies file within file system

Type – needed for systems that support different types

Location – pointer to file location on device

Size – current file size

Protection – controls who can do reading, writing, executing

Time, date, and user identification – data for protection, security, and usage monitoring

Information about files are kept in the directory structure, which is maintained on the disk

Page 5: Ch10

10.5 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Example of File AttributesExample of File Attributes

UNIX: ls -li

26047823 -rw-r--r-- 1 Salim staff 596480 Mar 16 20:17 Lecture10.ppt

Page 6: Ch10

10.6 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

File OperationsFile Operations

File is an abstract data type

File operations:

Create

Write

Read

Reposition within file

Delete

Truncate

Open(Fi) – search the directory structure on disk for entry Fi, and move the content of entry to memory

Close (Fi) – move the content of entry Fi in memory to directory structure on disk

Page 7: Ch10

10.7 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Open FilesOpen Files

Several pieces of data are needed to manage open files:

File pointer: pointer to last read/write location, per process that has the file open

File-open count: counter of number of times a file is open – to allow removal of data from open-file table when last processes closes it

Disk location of the file: cache of data access information

Access rights: per-process access mode information

Page 8: Ch10

10.8 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Open File LockingOpen File Locking

Provided by some operating systems and file systems

Mediates access to a file

Mandatory or advisory:

Mandatory – access is denied depending on locks held and requested

Advisory – processes can find status of locks and decide what to do

Page 9: Ch10

10.9 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

File Types – Name, ExtensionFile Types – Name, Extension

Page 10: Ch10

10.10 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Access MethodsAccess Methods

Sequential Accessread nextwrite next resetno read after last write

(rewrite) Direct Access

read nwrite nposition to n

read nextwrite next

rewrite n

n = relative block number

Page 11: Ch10

10.11 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Sequential-access FileSequential-access File

Page 12: Ch10

10.12 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Simulation of Sequential Access on a Direct-access FileSimulation of Sequential Access on a Direct-access File

Page 13: Ch10

10.13 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Example of Index and Relative FilesExample of Index and Relative Files

Page 14: Ch10

Directories Directories

Page 15: Ch10

10.15 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Directory StructureDirectory Structure

A collection of nodes containing information about all files

F 1 F 2F 3

F 4

F n

Directory

Files

Both the directory structure and the files reside on diskBackups of these two structures are kept on tapes

Page 16: Ch10

10.16 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

A Typical File-system OrganizationA Typical File-system Organization

Page 17: Ch10

10.17 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Operations Performed on DirectoryOperations Performed on Directory

Search for a file

Create a file

Delete a file

List a directory

Rename a file

Traverse the file system

Page 18: Ch10

10.18 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Organize the Directory (Logically) to ObtainOrganize the Directory (Logically) to Obtain

Efficiency – locating a file quickly

Naming – convenient to users

Two users can have same name for different files

The same file can have several different names

Grouping – logical grouping of files by properties, (e.g., all Java programs, all games, …)

Page 19: Ch10

10.19 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Single-Level DirectorySingle-Level Directory

A single directory for all users

Naming problem

Grouping problem

Page 20: Ch10

10.20 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Two-Level DirectoryTwo-Level Directory

Separate directory for each user

Path name

Can have the same file name for different user

Efficient searching

No grouping capability

Page 21: Ch10

10.21 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Tree-Structured DirectoriesTree-Structured Directories

Page 22: Ch10

10.22 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Tree-Structured Directories (Cont)Tree-Structured Directories (Cont)

Efficient searching

Grouping Capability

Current directory (working directory)

cd /spell/mail/prog

type list

Page 23: Ch10

10.23 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Tree-Structured Directories (Cont)Tree-Structured Directories (Cont)

Absolute or relative path name Creating a new file is done in current directory Delete a file

rm <file-name> Creating a new subdirectory is done in current directory

mkdir <dir-name>

Example: if in current directory /mail

mkdir count

mail

prog copy prt exp count

Deleting “mail” deleting the entire subtree rooted by “mail”

Page 24: Ch10

10.24 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Acyclic-Graph DirectoriesAcyclic-Graph Directories

Have shared subdirectories and files

Page 25: Ch10

10.25 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Acyclic-Graph Directories (Cont.)Acyclic-Graph Directories (Cont.)

Two different names (aliasing)

If dict deletes list dangling pointer

Solutions:

Backpointers, so we can delete all pointersVariable size records a problem

Backpointers using a daisy chain organization

Entry-hold-count solution

New directory entry type

Link – another name (pointer) to an existing file

Resolve the link – follow pointer to locate the file

Page 26: Ch10

10.26 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

General Graph DirectoryGeneral Graph Directory

Page 27: Ch10

10.27 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

General Graph Directory (Cont.)General Graph Directory (Cont.)

How do we guarantee no cycles?

Allow only links to file not subdirectories

Garbage collection

Every time a new link is added use a cycle detectionalgorithm to determine whether it is OK

Page 28: Ch10

10.28 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

File System MountingFile System Mounting

A file system must be mounted before it can be accessed

A unmounted file system (i.e. Fig. 11-11(b)) is mounted at a mount point

Page 29: Ch10

10.29 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

(a) Existing. (b) Unmounted Partition(a) Existing. (b) Unmounted Partition

Page 30: Ch10

10.30 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Jan 1, 2005

Mount PointMount Point