Mass-Storage Devices: Disks. CSCI 5103 Operating Systems. Basic Disk Functionality. Magnetic Disks

Transcription

1 Mass-Storage Devices: Disks CSCI 5103 Operating Systems Instructor: Abhishek Chandra Disk Structure and Attachment Disk Scheduling Disk Management RAID Structure Stable Storage 2 Magnetic Disks Most common form of secondary storage Basic structure: Platter with read-write head Multiple platters can be in a single disk drive Disk geometry: Track: Concentric circular region which contains data Cylinder: Set of tracks across multiple platters Sector: Chunk of data within a track Basic Disk Functionality Platter rotates at high speeds Disk head flies close to the platter surface Transfers data from one or more sectors to external I/O bus Reading/writing data Seek time: Time to move head to right track Latency time: Time for right sector to come under head Transfer time: Time to move desired no. of bytes 3 4 1

2 Other Storage Media Solid-State Disks (SSDs) Non-volatile memory. E.g.: Flash, DRAM+battery Faster but costlier than magnetic disks No moving parts, no seek/rotational latency Reads faster than writes, limited write lifetime Usage: Smaller devices, Caches in multi-tier storage, Metadata storage in storage arrays Magentic Tapes Large capacity and low cost Much slower than disks, sequential access Usage: Backup and archiving Disk Attachment Disk drive connected to a host computer Host controller: Controller device at host Issues I/O instructions, controls data transfer to memory Device controller: Controller on the disk Operates disk hardware based on I/O command Can cache data read from disk I/O bus: Channel connecting the two Transfers data from device to host May write directly to memory via memorymapped I/O Types of Disk Attachment Host-attached storage Disk attached directly to host machine I/O happens via local I/O ports E.g.: IDE, ATA, SCSI, FiberChannel Network-attached storage (NAS) Disks are accessed over a network Data transferred over TCP/IP E.g.: iscsi Storage-area network (SAN) Devices connected over a separate network Clients access data via servers E.g.: FC, iscsi, Infiniband 8 Disk Scheduling File system may issue several disk requests Each request contains info about: I/O type (read/write) Disk location (track, sector no.) Amount of data (how many bytes or sectors) Question: What order should these requests be scheduled on the disk? 2

3 Disk Scheduling Algorithms Goals: Maximize disk throughput Also achieve fairness, low response times, etc. How is disk scheduling different from CPU scheduling? FCFS Service requests in order of arrival Problems? 9 10 Shortest-Seek Time First (SSTF) Tries to minimize seek time for each request Move to the closest request in terms of seek time Problem? SCAN (Elevator) Algorithm Sweeps from one end of disk to the other Services requests in order during each sweep What happens to the request wait times for requests at different ends of the disk?

4 Circular SCAN (C-SCAN) Moves back to beginning of disk after each sweep Services the tracks in circular order Achieves a more uniform wait time than SCAN LOOK Algorithm Variant of SCAN, C-SCAN Does not go to end of disk Goes till the last request at each end Selection of Disk Scheduling Algorithm Depends on: Workload, desired metrics File allocation method: contiguous vs. indexed Placement of data vs. metadata Disk controller-level scheduling: Has better understanding of disk geometry, rotational latencies Why not leave scheduling to disk controller? Has limited queue space Non-performance considerations: Fairness Priority: e.g., metadata vs. data Differentiation: e.g., demand paging vs. file I/O I/O type: reads vs. writes

5 Disk Management How does the OS manage disk storage and usage? Formatting Handling bad blocks Swap space management Disk Formatting Physical formatting Create sectors: header, trailer, and data area Header, trailer: sector number, ECC Done at disk manufacturing time OS formatting: Partitioning: Divide disk into groups of cylinders Logical formatting: Initial file system data structures (free blocks, inodes, etc.) stored on disk Raw partition: No file system structures created, sequence of logical blocks provided Disk Partitions Raw partition: No file system E.g.: Swap space, Databases Boot partition: Used to boot system Sequence of blocks, loaded into memory Boot loader executed from pre-defined location Finds kernel on disk and loads into memory Root partition: Contains kernel and other system files Mounted at boot-time Handling Bad Blocks Some sectors may be corrupted How to handle bad blocks? Manual handling: Find and isolate bad blocks during formatting or consistency checking Sector sparing: Spare sectors maintained on disk Disk controller logically replaces bad sector with spare Sector slipping: Cascading copy of sequence of sectors to a distant spare sector

6 Swap Space Management Where is swap space allocated? Swap file: Uses file system services for creation, allocation, I/O Swap partition: Raw partition, has its own storage manager Pros and cons: Swap file: Easier to implement, higher overhead Swap partition: More efficient in terms of access time, might waste more space Linux Swap Space Allows both swap file or partition Swap space used only for: Anonymous memory: Stack, heap, uninitialized data Code segments read directly from file, thrown away Shared pages Page slots: contain swapped out pages Swap map: array of counters for page slots Counter indicates no. of mappings to page Stable Storage Ensure that data is never lost or corrupted Disk writes happen correctly Protect against: Disk write errors Disk blocks going bad CPU crash during disk writes Useful for transactions, backups, and logging Stable Storage Implementation Maintain two physical blocks for each logical block Each block typically on a separate disk Assumptions: Write errors can be detected (e.g., using ECC) Probability of both blocks getting corrupted is negligible Possible outcomes of a disk write Success: New data written correctly Partial failure: Data corruption, detectable error Total failure: Error before start of write, so old data is correct

7 Stable Storage Operation Stable write: Write to first block, then write to second block If both writes succeed correctly, then success Stable read: First read from block 1 If error detected, read from block 2 Recovery: If both blocks good and same data, no action If one block has error, copy data from good block If both blocks good but different data, copy from block 1 to 2 RAID Redundant Array of Independent Disks A set of disks used together to store data Goals: Reliability, performance Reliability: Data placed redundantly on multiple disks Performance: Data can be read in parallel from multiple disks RAID Techniques: Reliability Mirroring: Create a duplicate Each logical disk consists of two physical disks Each write sent to both, read from either Error correcting codes: Add redundant parity bits to detect and/or correct errors Parity bits placed on separate disks from data Single parity bit: Can detect one bit flip Hamming code: Multiple parity bits added to detect and correct bit error Block-parity: ECC for block of data. E.g.: Parity block, Reed-Solomon code RAID Techniques: Performance Striping: Split data across multiple disks Bit-level: Split each byte across disks Block-level: File blocks split across disks Others: byte-level, sector-level striping Performance improvement: Higher throughput of small accesses (via load balancing) Lower response time for large accesses (via parallelism)

8 RAID Levels Different combinations of striping and redundancy RAID 0: Non-redundant striping Block-level striping, no redundancy Performance vs. reliability? RAID 1: Mirroring No striping Performance vs. reliability? RAID 2: Memory-style ECC Add parity bits for error correction: Hamming code Bit-level striping of data+parity bits How many additional disks needed for 4 data disks? RAID Levels RAID 3: Bit-interleaved parity Disk controller can detect which sector is bad Need only one parity bit to detect and correct error Space overhead? RAID 4: Block-interleaved parity Block-level striping Parity block on additional disk RAID 5: Block-interleaved distributed parity Similar to RAID 4 Spreads data and parity blocks across all disks Benefit? RAID Levels RAID 6: P+Q redundancy Similar to RAID 5 Adds additional redundant blocks to recover from multiple disk failures Nested RAID: Combine multiple RAID levels Goal: Achieve both performance and reliability RAID 0+1: Striping followed by mirroring RAID 1 applied on set of RAID 0 s treated as disks RAID 1+0: Mirroring followed by striping RAID 0 applied on set of RAID 1 s treated as disks More robust to multiple disk failures 31 8