ACM Home Page
Please provide us with feedback. Feedback
Ivy: a read/write peer-to-peer file system
Full text PdfPdf (1.65 MB)
Source ACM SIGOPS Operating Systems Review archive
Volume 36 ,  Issue SI  (Winter 2002) table of contents
OSDI '02: Proceedings of the 5th symposium on Operating systems design and implementation
SPECIAL ISSUE: Decentralized storage systems table of contents
Pages: 31 - 44  
Year of Publication: 2002
ISSN:0163-5980
Authors
Athicha Muthitacharoen  MIT Laboratory for Computer Science, Cambridge, MA
Robert Morris  MIT Laboratory for Computer Science, Cambridge, MA
Thomer M. Gil  MIT Laboratory for Computer Science, Cambridge, MA
Benjie Chen  MIT Laboratory for Computer Science, Cambridge, MA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 3,   Downloads (12 Months): 30,   Citation Count: 3
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/844128.844132
What is a DOI?

ABSTRACT

Ivy is a multi-user read/write peer-to-peer file system. Ivy has no centralized or dedicated components, and it provides useful integrity properties without requiring users to fully trust either the underlying peer-to-peer storage system or the other users of the file system.An Ivy file system consists solely of a set of logs, one log per participant. Ivy stores its logs in the DHash distributed hash table. Each participant finds data by consuiting all logs, but performs modifications by appending only to its own log. This arrangement allows Ivy to maintain meta-data consistency without locking. Ivy users can choose which other logs to trust, an appropriate arrangement in a semi-open peer-to-peer system.Ivy presents applications with a conventional file system interface. When the underlying network is fully connected, Ivy provides NFS-like semantics, such as close-to-open consistency. Ivy detects conflicting modifications made during a partition, and provides relevant version information to application-specific conflict resolvers. Performance measurements on a wide-area network show that Ivy is two to three times slower than NFS.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Planet Lab. http://www.planet-lab.org/.
2
3
 
4
B. Berliner. CVS II: Parallelizing software development. In Proc. Winter 1990 USENIX Technical Conference, 1990.
5
 
6
B. Callaghan, B. Pawlowski, and P. Staubach. NFS version 3 protocol specification. RFC 1813, Network Working Group, June 1995.
 
7
 
8
9
 
10
FIPS 180-1. Secure Hash Standard. U.S. Department of Commerce/N.I.S.T., National Technical Information Service, April 1995.
 
11
K. Fu, M. Frans Kaashoek, and D. Mazières. Fast and secure distributed read-only file system. In Proc. of the USENIX Symposium on Operating Systems Design and Implementation, pages 181--196, October 2000.
12
13
14
15
 
16
17
18
 
19
 
20
U. Maheshwari, R. Vingralek, and W. Shapiro. How to build a trusted database system on untrusted storage. In Proc. of the USENIX Symposium on Operating Systems Design and Implementation, pages 135--150, October 2000.
 
21
 
22
23
24
 
25
 
26
T. Page, R. Guy, G. Popek, and J. Heidemann. Architecture of the Ficus scalable replicated file system. Technical Report UCLA-CSD 910005, 1991.
 
27
D. Parker, G. Popek, G. Rudisin, A. Stoughton, B. Walker, E. Walton, J. Chow, D. Edwards, S. Kiser, and C. Kline. Detection of mutual inconsistency in distributed systems. In IEEE Transactions on Software Engineering, volume 9(3), pages 240--247, 1983.
 
28
29
30
31
32
 
33
R. Sandberg, D. Goldberg, D. Kleiman, D. Walsh, and B. Lyon. Design and implementation of the Sun network file system. In Proc. Usenix Summer Conference, pages 119--130, June 1985.
34
35
 
36
37
 
38
J. Strunk, G. Goodson, M. Scheinholtz, and C. Soules. Self-securing storage: Protecting data in compromised systems. In Proc. of the USENIX Symposium on Operating Systems Design and Implementation, pages 165--179, October 2000.
39
40
 
41


Collaborative Colleagues:
Athicha Muthitacharoen: colleagues
Robert Morris: colleagues
Thomer M. Gil: colleagues
Benjie Chen: colleagues