\nUnlike most data structures we've talked about in the past, file systems\nmust ____. That is, they must work properly despite situations such as a\n____ or system ____. When these events occur, the operating system must\nresolve the ____ problem, which is caused by the fact that the disk may\nonly complete a subset of the desired operations before the situation\nhappens and puts the file system in an ____ state.\n
\n\nTo put the file system back in order, we can use ____ or the file\nsystem checker which runs ____ the file system is mounted during boot.\nTo speed up this restoration process, modern file systems utilize ____,\nwhich adds a bit of overhead on each write, but allows them to quickly\nrecover from the events discussed above.
\n\n\n" }, "q06": { "type": "multiple", "question": "\n\nWhich of the following are possible causes of latent-sector errors or\nblock corruption?\n\n\n", "responses": { "cosmic": "Cosmic rays may flip bits.", "firmware": "Faulty firmware may incorrectly record data.", "crash": "Disk head might touch the platter and damage the surface.", "bus": "Data may be corrupted in transit." } }, "q07": { "type": "blank", "question": "\n\nThe primary mechanism for preserving data integrity is to ____ the data.\nThat is, we need to produce concise summaries of data blocks that can be\ncompared in the future. Ideally, the function we use to produce these\nsummaries would minimize ____ or situations where non-identical blocks\nproduce the same summary.\n\nWhile summaries allow us to detect block corruption, we still have the\nproblem of ____, where data is written to the wrong location. To solve\nthis, we need to add a ____ to record where the data is suppose to be\nstored.\n\nOnce we have these summaries, we can periodically perform ____, which\nchecks every block of the system and sees if the summaries are still\nvalid.\n\n\n" }, "q04": { "type": "order", "question": "\n\nMatch the following labels to the descriptions of what fsck does:\n\n