6.033 - Computer System Engineering | Handout 29 - Issued April 13, 2000 |
Read chapter 8, sections A and B and appendix 8-A to prepare for this lecture. Appendix 8-B is optional, but recommended.
Today's reading is "Disk system architectures for high performance computing" by Katz et al., reading #23. This paper describes how to build high-availability storage systems using disk arrays; its terminology is used by industry today. Sections I through IV can be skimmed; the key section to focus on is Section V. (If you aren't familiar with how disks work, it is worth reading the first four paragraphs of section II carefully and also paying a little, but not much, more attention to section IV.) .
Hands-onAthena uses the Andrew File System. In this hands-on assignment, we'd like you to explore how AFS is designed to protect against the loss of data if any system failures occur.
AFS uses replication to protect critical volumes from failure. One of the most important volumes is the root volume since all lookups must proceed from there. Run the command:
vos examine root.cellto see what sites have replicas of the root volume.
First, read chapter 8, appendix 8-C, which provides some guidance on the real reading assignment, which is "The recovery manager of the system R database manager" by Gray et al., reading #25. This paper is a heavy duty paper, but contains important, well-explained information. Pay attention to the details. Why did the RSS turn out to be so complex? How does shadowing work? What useful features and functionality does the log provide? How is consistency and serializability obtained?
Read chapter 8, sections C (pages 8-37 to 8-44) and the remaining part of section D (8-D.2 to 8-D.4, pages 8-51 to 8-58) to prepare for this lecture.
Design Project 2 is due today. Remember to turn in two
copies of your report (one with the names of the group members and
another with a 6-digit code instead; put the code on your signed copy
as well). Please, pick your own 6-digit nonce. The second copy of
your report will go to some other group in the class (and your group,
in turn, will receive a copy of another report) for grading and
comments. This time the late policy is simple: there are
absolutely no extensions.
System aphorism of the week
An engineer is a person who can
do for a dime what any fool can do for a dollar. (Anonymous)
Go to 6.033 Home Page | Questions or Comments: 6.033-tas@mit.edu
|