The Coda Distributed File System Export

@article{braam:coda, address = {Seattle, WA, USA}, author = {Braam, Peter J.}, citeulike-article-id = {570862}, citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=327403}, comment = {having a server-based fs greatly simplifies a number of issues ---=note-separator=--- problems facing the design of a good distributed fs: 1. transport performance + latency 2. security of data 3. failures - network + server ---=note-separator=--- client access to coda - not to a server but system as a whole caching via Venus - (connected) caches all files, writes are done on cache, updates are sent to server when file is closed (disconnected) updates are stored in client modification log (CML) and re-integrated (merged) when system comes online important files are hoarded - frequently updated cache copies ---=note-separator=--- volumes are small filesystems directories files volumes can be replicated in a volume server group (VSG) -- resolution of conflicts is done via version stamps}, issn = {1075-3583}, journal = {Linux J.}, keywords = {abcsg\_dm, afs, coda, dfs, distributed-file-system}, number = {50es}, posted-at = {2006-03-30 16:07:52}, priority = {0}, publisher = {Specialized Systems Consultants, Inc.}, title = {The Coda Distributed File System}, url = {http://portal.acm.org/citation.cfm?id=327403}, volume = {1998}, year = {1998} }

TY - JOUR ID - braam:coda L3 - citeulike-article-id:570862 IS - 50es JF - Linux J. SN - 1075-3583 AD - Seattle, WA, USA TI - The Coda Distributed File System PB - Specialized Systems Consultants, Inc. VL - 1998 KW - abcsg_dm KW - afs KW - coda KW - dfs KW - distributed-file-system N1 - having a server-based fs greatly simplifies a number of issues N1 - problems facing the design of a good distributed fs: 1. transport performance + latency 2. security of data 3. failures - network + server N1 - client access to coda - not to a server but system as a whole caching via Venus - (connected) caches all files, writes are done on cache, updates are sent to server when file is closed (disconnected) updates are stored in client modification log (CML) and re-integrated (merged) when system comes online important files are hoarded - frequently updated cache copies N1 - volumes are small filesystems directories files volumes can be replicated in a volume server group (VSG) -- resolution of conflicts is done via version stamps AU - Braam, Peter PY - 1998/// UR - http://portal.acm.org/citation.cfm?id=327403 ER -