File System Usability
Photo by
Element5 Digital
from
Pexels
So we've learned how to store bits on the disk, but how can we make sure we know which bits are where? And that our user does, too?
Learning Objectives
It's time to make stable storage usable for our users!
Upon completion of this module, you will be able to:
- Describe the file system API and its purpose.
- Assess the advantages and disadvantages of directory structures.
- Trace the steps of various file systems to access or store files.
- Design a file system based on the requirements and characteristics of a system.
Learning
- Video: File System Usability (3 minutes)
- Video: Directories (7 minutes)
- Video: Finding a File (6 minutes)
- Video: Finding a File: Another Example (7 minutes)
- Video: Putting It All Together (5 minutes)
- Video: Optimizations (2 minutes)
- Video: File System API (5 minutes)
- Slides that were presented in the videos.
Note that these videos have embedded formative assessments ---you'll want to watch the videos and complete those before class, so that you can earn participation credit.
Recommended Readings
Completing the readings in this class is highly recommended---it can be very helpful to see how the concepts are explained by a different person, and the extra details can help the pieces fit together.
OSTEP: Files and Directories
From Class
Evaluating Your Understanding
We are providing these rubrics for each module so that you can better understand what is expected and evaluate your understanding against those expectations. The hope is that, if you find yourself earning a 3 or below, you will continue to enhance your understanding until you find yourself earning a 4 or a 5.
| Standards for File Systems Sub-Competency | 5 | 4 | 3 | 2 |
|---|---|---|---|---|
| File Systems | Student accurately describes the file system API, accurately assesses the advantages and disadvantages of directory structures, accurately traces the steps of various file systems to access or store files, and accurately designs a file system based on the requirements and characteristics of a system. | Student accurately describes the file system API, satisfactorily assesses the advantages and disadvantages of directory structures, accurately traces the steps of various file systems to access or store files, and satisfactorily designs a file system based on the requirements and characteristics of a system. | Student satisfactorily describes the file system API, unsatisfactorily assesses the advantages and disadvantages of directory structures, satisfactorily traces the steps of various file systems to access or store files and unsatisfactorily designs a file system based on the requirements and characteristics of a system. | Student unsatisfactorily describes the file system API, unsatisfactorily assesses the advantages and disadvantages of directory structures, unsatisfactorily traces the steps of various file systems to access or store files, and unsatisfactorily designs a file system based on the requirements and characteristics of a system. |
| File Systems Project | Student submitted project that 1) when executed, passes all test cases, including accurately transferring data from main memory to disk and extending the file system to allow for file growth, a hierarchical directory structure, and concurrent access, 2) when visually inspected, does not reveal any race conditions or concurrency errors, 3) includes a design document that accurately describes the code and answers the given questions, and 4) follows all given formatting guidelines. | Student submitted project that 1) when executed, passes most test cases, including satisfactorily transferring data from main memory to disk and extending the file system to allow for file growth, a hierarchical directory structure, and concurrent access, 2) when visually inspected, does reveal one or no race conditions or concurrency errors, 3) includes a design document that satisfactorily describes the code and answers the given questions, and 4) follows most given formatting guidelines. | Student submitted project that 1) when executed, passes some test cases, including unsatisfactorily transferring data from main memory to disk and extending the file system to allow for file growth, a hierarchical directory structure, and concurrent access, 2) when visually inspected, does reveal a few race conditions or concurrency errors, 3) includes a design document that unsatisfactorily describes the code and answers the given questions, and 4) follows few given formatting guidelines. | Student fails to submit the project or submitted project that 1) when executed, passes no or few test cases, including incorrectly transferring data from main memory to disk and extending the file system to allow for file growth, a hierarchical directory structure, and concurrent access, 2) when visually inspected, does reveal many race conditions or concurrency errors, 3) includes a design document that incorrectly describes the code and answers the given questions, and 4) follows few given formatting guidelines. |
| Short Answer Questions: File System-Specific | Student submitted answers to given questions that accurately and succinctly answer the questions. | Student submitted answers to given questions that satisfactorily and succinctly answer the questions. | Student submitted answers to given questions that unsatisfactorily answer the questions. | Student does not submit the answers OR submitted answers to given questions that incorrectly answer the questions. |
| Short Answer Questions: File systems as part of the larger system | Student submitted answers to given questions that accurately and succinctly answer the questions. | Student submitted answers to given questions that satisfactorily and succinctly answer the questions. | Student submitted answers to given questions that unsatisfactorily answer the questions. | Student does not submit the answers OR submitted answers to given questions that incorrectly answer the questions. |