Module 4

File System
Implementation
 File-System Structure
• Disks provide the bulk of secondary storage on which a file system is
maintained.
• They have two characteristics that make them a convenient medium for storing
multiple files:
1. A disk can be rewritten in place; it is possible to read a block from the disk,
modify the block, and write it back into the same place.
2. A disk can access directly any given block of information it contains.
• I/O transfers between memory and disk are performed in units of blocks.
• A file system poses two quite different design problems.
1. Defining how the file system should look to the user.
2. Creating algorithms and data structures to map the logical file system onto
the physical secondary-storage devices.
• The file system itself is generally composed of many different levels.
• The file-organization module knows about files and their logical blocks, as well as
physical blocks.
• The logical file system manages metadata information(via FCB).
File-System Structure
• The lowest level, the I/O control, consists
of device drivers and interrupt handlers to
transfer information between the main
memory and the disk system.
• The basic file system needs only to issue
generic commands to the appropriate
device driver to read and write physical
blocks on the disk

Layered File System

 File-System Implementation
• System calls are responsible for providing access for the file contents to the
process.
• On-disk and in-memory structures are used to implement the file system.
• On-disk File system
1. Boot control block contains info needed by system to boot OS from that volume
(usually first block of volume)
2. Volume control block (superblock, master file table) contains volume details(Total
no of blocks, no of free blocks, block size, free block pointers or array)
3. Directory structure per file system -> organizes the files(Names and inode
numbers, master file table)
4. Per file FCB contains many details about the file(Typically, inode number,
permissions, size, dates, location of the file blocks)
File-System Implementation
• In-Memory File System Structures: used for both file system
management and performance improvement via caching.
• Here data will be loaded at mount and discarded at dismount time
1. In-memory Mount table storing file system mounts, mount points,
file system types.
2. In-memory directory structure holds directory information os
recently accessed directories.
3. System-wide open-file table contains a copy of the FCB of each open
file and other information
4. Per-process open-file table contains pointers to appropriate entries in
system-wide open-file table as well as other information.
Creation of new file system:
Application program calls -> logical file system -> allocated new FCB ->
System then reads the directory to memory -> update the new file name
and FCB and writes back to disk.
• Figure 12-3(a) refers to opening a file
• Figure 12-3(b) refers to reading a file
 Virtual File Systems
• Multiple file types are supported in modern OS
• How OS allow these FS to be integrated with directory?
• How users can navigate b/w FS space?
• Most OS used object oriented technique to simplify, organize and
modularize the implementation.
• The virtual file system (VFS) layer
serves two important functions:
1. It separates file-system-generic
operations from their
implementation by defining
a clean VFS interface.
2. provides a mechanism for
uniquely representing a file
throughout a network
using vnode.
Directory Implementation
• Linear list of file names with pointer to the data blocks
• Simple to program
• Time-consuming to execute
• Linear search time
• Could keep ordered alphabetically via linked list or use B+ tree
• Hash Table – linear list with hash data structure
• Decreases directory search time
• Collisions – situations where two file names hash to the same location
• Only good if entries are fixed size, or use chained-overflow method
 Allocation Method
• An allocation method refers to how disk blocks are
allocated for files:
• Contiguous
• Linked
• File Allocation Table (FAT)
Contiguous Allocation Method
• An allocation method refers to how disk blocks are allocated for files:
• Each file occupies set of contiguous blocks
• Best performance in most cases
• Simple – only starting location (block #) and length (number of blocks) are
required
• Problems include:
• Finding space on the disk for a file,
• Knowing file size,
• External fragmentation.
Contiguous Allocation (Cont.)
• Mapping from logical to physical
(block size =512 bytes)
Q

LA/512

• Block to be accessed = starting

address + Q
• Displacement into block = R
Linked Allocation
• Each file is a linked list of blocks
• File ends at nil pointer
• No external fragmentation
• Each block contains pointer to next block
• Free space management system called when new block needed
• Improve efficiency by clustering blocks into groups but increases
internal fragmentation
• Reliability can be a problem
• Locating a block can take many I/Os and disk seeks
Linked Allocation Example
• Each file is a linked list of disk blocks: blocks may be scattered
anywhere on the disk
• Scheme
• 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
FAT Allocation Method
• Beginning of volume has table, indexed by block number
• Much like a linked list, but faster on disk and cacheable
• New block allocation simple
 Indexed Allocation Method
• Each file has its own index block(s) of pointers to its data blocks
• Logical view

index table
 Indexed Allocation – Small Files
• Need index table
• Random access
• Dynamic access without external fragmentation, but have overhead of index
block
• Mapping from logical to physical in a file of maximum size of 256K bytes and
block size of 512 bytes. We need only 1 block for index table
Q

LA/512

• Calculation:
• Q = displacement into index table
• R = displacement into block
 Indexed Allocation – Large Files
• Mapping from logical to physical in a file of unbounded length (block size of
512 words)
• Linked scheme – Link blocks of index table (no limit on size)
• Multi-level indexing
• Combination of both linked and multi-level scheme
Performance
• Best method depends on file access type
• Contiguous great for sequential and random
• Linked good for sequential, not random
• Declare access type at creation
• Select either contiguous or linked
• Indexed more complex
• Single block access could require 2 index block reads then data block read
• Clustering can help improve throughput, reduce CPU overhead
 Free-Space Management
• File system maintains free-space list to track available blocks
• Bit vector or bit map (n blocks)

01 2 n-1
…


1  block[i] free
bit[i] =
0  block[i] occupied
• Bit map requires extra space
• Example:
block size = 4KB = 212 bytes
disk size = 240 bytes (1 terabyte)
n = 240/212 = 228 bits (or 32MB)
if clusters of 4 blocks -> 8MB of memory

• Easy to get contiguous files

 Linked Free Space List on Disk

▪ Linked list (free list)

• Cannot get contiguous space
easily
• No waste. Linked Free Space
List on Disk of space
• No need to traverse the entire list
(if # free blocks recorded)
 Free-Space Management (Cont.)
• Grouping
• Modify linked list to store address of next n-1 free blocks in first free
block, plus a pointer to next block that contains free-block-pointers
(like this one)

• Counting
• Because space is frequently contiguously used and freed, with
contiguous-allocation allocation, extents, or clustering
• Keep address of first free block and count of following free blocks
• Free space list then has entries containing addresses and counts