Consistency of file systems

The UFS file system relies on an internal set of tables to keep track of inodes used and available blocks. When these internal tables are not properly synchronized with data on a disk, inconsistencies result and file systems need to be repaired.

File systems can be inconsistent because of abrupt termination of the operating system in these ways:. Skip to content. Change Language. Related Articles. Table of Contents.

Improve Article. Save Article. Like Article. Last Updated : 23 Jun, Previous Bulma Box. Recommended Articles. It was originally developed by Carnegie Mellon University as part of the Andrew project. Referring to Carnegie as Andrew Mellon. Its main use is widespread in computer science. Which of the following file system provides similar features that are also offered by the Andrew File System? AFS [3] has a number of implications for traditional network file systems, primarily in terms of security and ease of scalability.

Each client caches files on the local file system itself to speed up subsequent requests to the same database. It also provides quick access to the file system in the event of server or hardware failure.

AFS uses a low consistency model. When the changed file is closed, the changed dishes are copied to the server. The consistency cache is stored using a callback mechanism. If the file is likely to be cached, the server will point this out and promise to notify the client if the file is clearly being updated by someone else. Callbacks are ignored and should be received after any client, server, or online connection failure, including a timeout.

Restoring the callback involves a health check and does not require replaying the main file itself.