1. COP 5611 Operating Systems Spring 2010 Dan C. Marinescu Office: HEC 439 B Office hours: M-Wd 1:00-2:00 PM

2. 2 22222 Lecture 13 Reading Assignment: Chapter 8 from the online textbook Homework 3 due on March 3 Midterm: Wednesday March 17, the first week after Spring Break Last time:  End-to-end-layer  Resource Management - Congestion Today:  Faults, Failures and Fault-Tolerant Design  Measures of Reliability and Failure Tolerance  Tolerating active Faults Next time

3. Reliable Systems from Unreliable Components Problem investigated first in mid 1940s by John von Neumann. Steps to build reliable systems  Error detection Network protocols (link and end-to-end)  Error containment – limit the effect of errors Enforced modularity: client-server architectures, virtual memory, etc.  Error masking – ensure correct operation in the presence of errors Network protocols: error correction, repetition, interpolation for data cu real- time constrains 3

4. Faults and errors Fault  a flaw with the potential to cause problems  Software  Hardware  Design  Implementation  Operation  Environment Types of faults  Latent  Active Error  the consequence of an active fault. 4

5. Error containment in a layered system Several design strategies are possible. The layer where an error occurs:  Masks the error  correct it internally so that the higher layer is not aware of it.  Detects the error and report its to the higher layer  fail-fast.  Stops  fail-stop.  Does nothing. Types of faults  Transient (caused by passing external condition)/Persistent  Soft /Hard  Can be masked or not by a retry.  Intermittent  occurs only occasionally and it is not reproducible Latency of a fault – time until a fault causes an error  A long latency may allow errors to accumulate and defeat periodic error correction 5

6. The fault-tolerance design process is iterative 1. Begin the design of a fault-tolerant model 1. Identify potential faults 2. Estimate the risk of each one 3. Design methods to detect the errors for the highest risk faults. 4. Design methods to deal with the errors for the highest risk faults 2. Contain the damage from high risk errors through modularity. 3. Design procedures to contain the errors detected by: 1. Temporal redundancy (retry the operation) 2. Spatial redundancy (deploy multiple components) 4. Update the model to account for the error masking procedures 5. Iterate until the probability of un-tolerated faults is small 6. Observe the system in the real world 1. Study the error logs 2. Identify the cause of each error 7. Use the information collected to improve the model and iterate again 6

7. Measures of reliability TTF – time to failure  MTTF – mean time to failure MTTF = 1/N ∑ TTF i TTR – time to repair  MTTR – mean time to repair MTTR = 1/N ∑ TTR i MTBF – mean time between failures MTBF =MTTF + MTTR Availability =MTTF/MTBF Down time = ( 1- Availability) = MTTR/MTBF 7

8. The conditional failure rate 8

9. Reliability functions Unconditional failure rate f(t) = Pr(module fails between t and t = dt) Reliability R(t) = Pr(module functions at time t given that it was functioning at time 0). This function is memoryless 9

10. 10

11. 11

12. 12

13. 13