Content deleted Content added
Citation bot (talk | contribs) m Add: date, citeseerx. Removed parameters. | You can use this bot yourself. Report bugs here. | User-activated. |
→Features: merge "i.e" parenthetical into the sentence as an "e.g.", styling it similarly |
||
Line 12:
|edition = Distributed Storage: Concepts, Algorithms, and Implementations
|date = 2013
}}</ref> Read and write operations on an open file are directed only to the locally cached copy. When a modified file is closed, the changed portions are copied back to the file server. Cache consistency is maintained by [[Callback (computer science)|callback]] mechanism. When a file is cached, the server makes a note of this and promises to inform the client if the file is updated by someone else. So if Callbacks are discarded and must be re-established after any client, server, or network failure, including a time-out. Re-establishing a callback involves a status check and does not require re-reading the file itself.
A consequence of the [[file locking]] strategy is that AFS does not support large shared databases or record updating within files shared between client systems. This was a deliberate design decision based on the perceived needs of the university computing environment. It leads, for example, to the use of a single file per message, like [[maildir]] does, in the original email system for the Andrew Project, the Andrew Message System, rather than a single file per mailbox
A significant feature of AFS is the [[Volume (computing)|volume]], a tree of files, sub-directories and AFS [[mount (computing)|mountpoints]] (links to other AFS volumes). Volumes are created by administrators and linked at a specific named path in an AFS cell. Once created, users of the filesystem may create directories and
| |||