Title: Mass Storage Structure
1Mass Storage Structure
2Chapter 14 Mass-Storage Systems
- 14.1 Disk Structure
- 14.2 Disk Scheduling
- 14.3 Disk Management
- 14.4 Swap-Space Management
- 14.5 RAID Structure
- 14.6 Disk Attachment
- 14.7 Stable-Storage Implementation
- 14.8 Tertiary Storage Devices
- 14.9 Operating System Issues
- 14.10 Performance Issues
3Hard Disks
Tanenbaum, Figure 5-25, Page 316
4Disk Structure
- Disk drives addressed as large 1-dimensional
arrays of logical blocks. - The 1-dimensional array of logical blocks is
mapped into the sectors of the disk sequentially. - Starts at Sector 0 on the outermost cylinder.
- Proceeds in order through that track,
- then the rest of the tracks in that cylinder, and
- then through the rest of the cylinders
- from outermost to innermost.
14.1, Page 491
5Disk Scheduling
- OS seeks to optimize access time, consisting
mainly of - Seek time the time for the disk are to move the
heads to the cylinder containing the desired
sector. - Rotational latency the additional time waiting
for the disk to rotate the desired sector to the
disk head. - Disk bandwidth
- total number of bytes transferred, divided by the
total time taken (between the first request and
completion of last transfer).
14.2, Page 492
6Disk-Scheduling Algorithms
- FCFS least efficient, has no optimization
- First Come, First Served
- SSTF is fast, but does not optimized head
movement - Shortest Seek Time First
- SCAN orders requests on in out head movement
- Elevator algorithm
- C-SCAN circular SCAN, reads requests in one
direction - Blocks as circular list, by sawtooth head
motion - LOOK like SCAN, but limit in out head movement
- Move between max and min requested tracks
- C-LOOK like C-SCAN, but limit in out head moves
14.2, Pages 493 498
7Disk Scheduling
- Several algorithms exist to schedule the
servicing of disk I/O requests. - We illustrate them with a request queue (0-199).
- 98, 183, 37, 122, 14, 124, 65, 67
- Head pointer 53
14.2, Page 493
8First Come First Served
Illustration shows total head movement of 640
cylinders.
14.2.1, Figure 14.1, Page 14.1
9SSTF
- Selects the request with the minimum seek time
from the current head position. - SSTF scheduling is a form of SJF scheduling may
cause starvation of some requests. - Illustration shows total head movement of 236
cylinders.
14.2.1, Page 494
10SSTF
14.2.2, Figure 14.2, Page 494
11SCAN
- The disk arm starts at one end of the disk, and
moves toward the other end, servicing requests
until it gets to the other end of the disk, where
the head movement is reversed and servicing
continues. - Sometimes called the elevator algorithm.
- Illustration shows total head movement of 208
cylinders.
14.2.3, Page 495
12Elevator Algorithm
14.2.3, Figure 14.3, page 495, but this is
Tanenbaum Figure 5-28, page 320
13C-SCAN
- Provides a more uniform wait time than SCAN.
- The head moves from one end of the disk to the
other. servicing requests as it goes. When it
reaches the other end, however, it immediately
returns to the beginning of the disk, without
servicing any requests on the return trip. - Treats the cylinders as a circular list that
wraps around from the last cylinder to the first
one.
14.2.4, Page 496
14C-SCAN
14.2.4, Figure 14.4, Page 496
15C-LOOK
- Version of C-SCAN
- Arm only goes as far as the last request in each
direction, then reverses direction immediately,
without first going all the way to the end of the
disk.
14.2.5, Page 496 497
16C-LOOK
14.2.5, Figure 14.5, Page 497
17Selecting a Disk-Scheduling Algorithm
- SSTF is common and has a natural appeal
- SCAN and C-SCAN perform better for systems that
place a heavy load on the disk. - Performance depends on the number and types of
requests. - Requests for disk service can be influenced by
the file-allocation method. - The disk-scheduling algorithm should be written
as a separate module of the operating system,
allowing it to be replaced with a different
algorithm if necessary. - Either SSTF or LOOK is a reasonable choice for
the default algorithm.
14.2.6, Page 497
18Disk Formatting
- Physical Formatting
- Dividing a disk into sectors that the disk
controller can read and write. - Partitioning
- The coarsest logical unit of storage for a disk
system. - Normally, disk is partitioned into one or more
groups of cylinders. - Logical Formatting
- Making the file system within each partition
14.3, Page 499
19Physical Formatting
- Dividing a disk into sectors that the disk
controller can read and write. - Constant linear velocity
- Uniform bit density, variable disk speed with
head movement - More sectors on the outer tracks (e.g. CDs)
- Constant angular velocity
- Data more dense toward inner tracks, to keep
equal sectors
Data
ECC
Preamble
Sector
Start code, cylinder, sector
256, 512 or 1024 bytes
Error Correction Codes
Tanenbaum, Figure 5-24, Page 315
20Disk Formatting
- Partitioning
- The coarsest logical unit of storage for a disk
system. - Logically, each partition is like a separate
disk. - Partition table is written at the end of the
master boot record - Logical Formatting
- High level format of each partition
- Making the file system within each partition
- Add boot block, free space list, root directory,
and empty file system
14.3.1, Page 499
21Typical File System Layout
Partition table
Disk partition
Boot block
Super block
Free space management
inodes
Root dir
Files
- Admin info
- File system type
- Number of blocks
Indexed file control block
Tanenbaum, Figure 6-11, Page 400
22MS-DOS Disk Layout
14.3.2, Figure 14.6, Page 501
23Bad Block Handling
- Manual
- Run chkdisk to search for bad blocks, lock them
away - Entry in FAT marks the block as bad (e.g. MS-DOS)
- Sector Sparing
- Controller maintains a list of bad blocks
- Have spare empty sectors for block replacement
- Sector Slipping
- Remap sectors to make sequential
- e.g. if 17 gone, and is spared at 202, then move
sectors 18 to 202 up by one until a spare is
created at 18
14.3.3, Pages 500 501
24Swap-Space Management
- Swap-space
- Disk space as an extension of main memory.
- Set up as a file in the normal file system
- Slower to navigate disk-allocation data
structures - Separate disk partition (more usual)
- Uses separate swap space storage manager
- allocate and deallocate blocks
- Optimized for speed rather than storage
efficiency - Solaris 2 makes both types available
14.4, Pages 502
25Swap-Space Management in UNIX
- 4.3 BSD
- Allocates swap space when process starts
- Holds text segment (the program) and data
segment. - e.g. two users of an editor share text segment,
have own data segments - Kernel uses swap maps to track swap-space use for
text and data segments separately. - Solaris 1
- Read text, throw it away if not needed in memory
- Solaris 2
- Solaris 2 allocates swap space only when a page
is forced out of physical memory, not when the
virtual memory page is first created.
14.4.3, 503
264.3 BSD Swap Maps
Text Segment
Data Segment
Expandable blocks
14.4.3, Figures 14.7, 14.8, page 504
27RAID Structure
- RAID
- Redundant Array of Independent Disks
- Provides reliability via redundancy.
- Inexpensive disks no longer the issue
- Reliability
- E.g. if mean time between failures (MTBF) is
100,000 hours for a disk, and there are 100
disks, then a disk fails every 1000 hours 40
days - E.g. in a mirrored two-disk system, if MTBF
100,000 hours and mean time to repair is 10
hours, then mean time to data loss is
100,0002/(210) 57,000 years.
14.5, 14.5.1, Page 505
28RAID
- Disk striping for speed of reading
- Split bits of each byte across several disks, or
- Place sequential blocks on different disks
- Speed increase by parallel access
- A group of disks work as one storage unit.
- RAID schemes improve performance and improve the
reliability of the storage system by storing
redundant data. - Mirroring or shadowing keeps duplicate of each
disk. - Block interleaved parity uses much less
redundancy.
14.5.2, Page 506
29RAID Levels
- 0. Block level striping with no redundancy
- Disk mirroring, keeping a second copy of data
- Bit level striping, with error correction bits
- Error checking parity bits all on one disk
- Block interleaves with parity block on one disk
- Block interleaves with distributed parity
- Error-correcting codes rather than parity bits
0. for high performance, less reliability 0 1
and 1 0 for performance plus reliability 5. For
reliable storage of large data volume
14.5.3, Pages 507 510
30RAID Levels
14.5.3, Figure 14.9, Page 507
31RAID (0 1) and (1 0)
14.5.3, Figure 14.10, Page 511
32Disk Attachment
- Local
- Host-attached storage via local I/O
- IDE, two disks per bus
- SCSI, 16 disks
- FC serial architecture, gt 128 disks
- Network
- Network Attached Storage (NAS)
- NFS for UNIX, CIFS for Windows
- RPCs carried over TCP/IP or UDP/IP
- Convenient, but less efficient than local
14.6, Pages 512 513
33Network-Attached Storage
14.6, Figure 14.11, Page 513
34Storage-Area Network
Private network with storage protocols rather
than network protocols, takes load off LAN.
14.6, Figure 14.12, Page 514
35Stable-Storage Implementation
- Write-ahead log scheme requires stable storage.
- To implement stable storage
- Replicate information on more than one
nonvolatile storage media with independent
failure modes. - Update information in a controlled manner to
ensure that we can recover the stable data after
any failure during data transfer or recovery.
14.7, Page 515
36Tertiary Storage Devices
- Low cost is the defining characteristic of
tertiary storage. - Generally, tertiary storage is built using
removable media - E.g. floppy disks, CD-ROMs, tapes
14.8.1, Page 516
37Removable Disks
- Floppy disk thin flexible disk coated with
magnetic material, enclosed in a protective
plastic case. - Most floppies hold about 1 MB similar technology
is used for removable disks that hold more than 1
GB. - Removable magnetic disks can be nearly as fast as
hard disks, but they are at a greater risk of
damage from exposure.
14.8.1.1, Page 516
38Removable Disks
- A magneto-optic disk records data on a rigid
platter coated with magnetic material. - Laser heat is used to make a disk spot
susceptible to a weak magnetic field to record a
bit. - Laser light is also used to read data by
polarization rotation in disk spot magnetic field
(Kerr effect). - Optical disks employ special materials that are
altered by laser light. - E.g. crystalline surface is transparent,
amorphous surface is reflective - Low power laser reads, medium power melts to
crystalline, high power melts to amorphous
14.8.1.1, Page 516
39WORM Disks
- The data on read-write disks can be modified over
and over. - WORM (Write Once, Read Many Times) disks can be
written only once. - Thin aluminum film sandwiched between two glass
or plastic platters. - To write a bit, the drive uses a laser light to
burn a small hole through the aluminum
information can be destroyed but not altered. - Very durable and reliable.
- Read Only disks, such as CD-ROM and DVD, come
from the factory with the data pre-recorded.
14.8.1.1, Page 517
40Digital Versatile Disks
Aluminum reflector
Semi-reflective layer
Dual-layer DVD (17 GB)
0.4 micron pits, 0.74 ? between tracks, 0.65 ?
laser
0.8 micron pits, 1.6 ? between tracks, 0.78 ?
laser
Tanenbaum, Figure 5-23, Page 314
41Tapes
- Compared to a disk, a tape is less expensive and
holds more data, but random access is much
slower. - Tape is an economical medium for purposes that do
not require fast random access, e.g., backup
copies of disk data, holding huge volumes of
data. - Large tape installations typically use robotic
tape changers that move tapes between tape drives
and storage slots in a tape library. - stacker library that holds a few tapes
- silo library that holds thousands of tapes
- A disk-resident file can be archived to tape for
low cost storage the computer can stage it back
into disk storage for active use.
14.8.1.2, Page 517
42Operating System Issues
- Major OS jobs
- manage physical devices
- present a virtual machine abstraction to
applications - For hard disks, the OS provides two abstraction
- Raw device an array of data blocks.
- File system the OS queues and schedules the
interleaved requests from several applications.
14.8.2, Page 519
43Application Interface
- Most OSs handle removable disks almost exactly
like fixed disks a new cartridge is formatted
and an empty file system is generated on the
disk. - Tapes are presented as a raw storage medium,
i.e., and application does not not open a file on
the tape, it opens the whole tape drive as a raw
device. - Usually the tape drive is reserved for the
exclusive use of that application. - Since the OS does not provide file system
services, the application must decide how to use
the array of blocks. - Since every application makes up its own rules
for how to organize a tape, a tape full of data
can generally only be used by the program that
created it.
14.8.2.1, Page 519
44Tape Drives
- The basic operations for a tape drive differ from
those of a disk drive. - locate positions the tape to a specific logical
block, not an entire track (corresponds to seek). - The read position operation returns the logical
block number where the tape head is. - The space operation enables relative motion.
- Tape drives are append-only devices updating a
block in the middle of the tape also effectively
erases everything beyond that block. - An EOT mark is placed after a block that is
written.
14.8.2.1, Page 520
45File Naming
- The issue of naming files on removable media is
especially difficult when we want to write data
on a removable cartridge on one computer, and
then use the cartridge in another computer. - Contemporary OSs generally leave the name space
problem unsolved for removable media, and depend
on applications and users to figure out how to
access and interpret the data. - Some kinds of removable media (e.g., CDs) are so
well standardized that all computers use them the
same way.
14.8.2.2, Page 520
46Hierarchical Storage Management (HSM)
- A hierarchical storage system extends the storage
hierarchy beyond primary memory and secondary
storage to incorporate tertiary storage usually
implemented as a jukebox of tapes or removable
disks. - Usually incorporate tertiary storage by extending
the file system. - Small and frequently used files remain on disk.
- Large, old, inactive files are archived to the
jukebox. - HSM is usually found in supercomputing centers
and other large installations that have enormous
volumes of data.
14.8.2.3, Page 521
47Speed
- Two aspects of speed in tertiary storage are
bandwidth and latency. - Bandwidth is measured in bytes per second.
- Sustained bandwidth average data rate during a
large transfer of bytes/transfer time.Data
rate when the data stream is actually flowing. - Effective bandwidth average over the entire I/O
time, including seek or locate, and cartridge
switching.Drives overall data rate.
14.8.3.1, Page 522
48Speed
- Access latency amount of time needed to locate
data. - Access time for a disk move the arm to the
selected cylinder and wait for the rotational
latency lt 35 milliseconds. - Access on tape requires winding the tape reels
until the selected block reaches the tape head
tens or hundreds of seconds. - Generally, random access within a tape cartridge
is about a thousand times slower than random
access on disk. - The low cost of tertiary storage is a result of
having many cheap cartridges share a few
expensive drives. - A removable library is best devoted to the
storage of infrequently used data, because the
library can only satisfy a relatively small
number of I/O requests per hour.
14.8.3.1, Page 522
49Reliability
- A fixed disk drive is likely to be more reliable
than a removable disk or tape drive. - An optical cartridge is likely to be more
reliable than a magnetic disk or tape. - A head crash in a fixed hard disk generally
destroys the data, whereas the failure of a tape
drive or optical disk drive often leaves the data
cartridge unharmed.
14.8.3.2, Page 523
50Cost
- Main memory is much more expensive than disk
storage - The cost per megabyte of hard disk storage is
competitive with magnetic tape if only one tape
is used per drive. - The cheapest tape drives and the cheapest disk
drives have had about the same storage capacity
over the years. - Tertiary storage gives a cost savings only when
the number of cartridges is considerably larger
than the number of drives.
14.8.3.3, Page 524
51Price per Megabyte of DRAM1981 2000
103
14.8.3.3, Figure 14.13, Page 524
52Price per Megabyte of Magnetic Hard Disk, 1981
2000
104
14.8.3.3, Figure 14.14, Page 525
53Price per Megabyte of a Tape Drive, 1984 2000
103
14.8.3.3, Figure 14.15, Page 526