Project 6 - File System

More documents

Recommendations

Info

<strong>Project</strong> 6 Concurrent Access UNIX read/write semantics II Simple ... but there are some traps that lead to integrity issues. Cannot just naively overwrite inodes as this leads to orphaned data blocks. You need consistent, synchronized metadata updates.
<strong>Project</strong> 6 Concurrent Access Alternative approaches ∗ : multi-read / single-write Concurrency happens at the “data blocks” level. Multiple individuals may hold the same file. Opening for writing always succeeds. At most one writer works simultaneously. Multi-block atomicity: let’s throw the end-to-end argument out the window. ∗ Alternative, as in we are not grading to these specifications
Page 1 and 2: Project 6 Project 6 File System Sea
Page 3 and 4: Project 6 Project Scope 1 Project S
Page 5 and 6: Project 6 Project Scope Our propose
Page 7 and 8: Project 6 Project Scope How does th
Page 9 and 10: Project 6 Implementation Details Cr
Page 11 and 12: Project 6 Implementation Details Th
Page 19 and 20: Project 6 Filesystem Structure A pi
Page 21 and 22: Project 6 Filesystem Structure The
Page 23 and 24: Project 6 Filesystem Structure File
Page 25 and 26: Project 6 Concurrent Access 1 Proje
Page 27: Project 6 Concurrent Access UNIX re
Page 31 and 32: Project 6 Concurrent Access Deletio
Page 33 and 34: Project 6 Considerations Keep inter
Page 35 and 36: Project 6 Considerations Efficiency
Page 37 and 38: Project 6 Considerations Testing Us
Page 39: Project 6 Considerations Concluding

Project 6 - File System

Create successful ePaper yourself

Delete template?

Save as template?