[39] in 6.033-lab
Extension + Clarification of assignment
daemon@ATHENA.MIT.EDU (Constantine P. Sapuntzakis)
Thu Apr 10 21:29:17 1997
To: 6.033-lab@MIT.EDU
Date: Thu, 10 Apr 1997 21:28:49 EDT
From: "Constantine P. Sapuntzakis" <csapuntz@MIT.EDU>
I've decided to move the preliminary design document to Monday to give
you time to meet with your groups and use the information you get in
recitation.
Also, there is only one library due PER GROUP and only one paper due PER
GROUP.
What I want to see in the paper:
1) Design goals/rationale
e.g. robustness, minimize seeks on writes,
2) Details of FS layout on disk (most important)
What do the on-disk data structures look like? Why
do they look that way? (what drove you to choose them?)
What are the performance characteristics?
3) Allocation strategies
How do you allocate files? What do you do when files grow?
How do you prevent/minimize fragmentation?
4) Pseudo-code
If it's non-obvious, describe how the on-disk structures
get updated for operations such as file creation and deletion.
Less important for now are:
1) In-memory data structures
How does the FS represent the on-disk data structure
when they are in core (a.k.a main memory)?
2) Robustness
How does the FS deal with catastrophic failure (machine shutdown)?
Losses of random sectors?
Your preliminary design is not cast in stone. You may feel free to
tinker with it as you may.
-Costa
csapuntz@mit.edu
