Results 1 -
3 of
3
NFS version 3: Design and implementation
- In Proceedings of the Summer 1994 USENIX Technical Conference
, 1994
"... This paper describes a new version of the Network File System (NFS) that supports access to files larger than 4GB and increases sequential write throughput sevenfold when compared to unaccelerated NFS Version 2. NFS Version 3 maintains the stateless server design and simple crash recovery of NFS Ver ..."
Abstract
-
Cited by 71 (0 self)
- Add to MetaCart
This paper describes a new version of the Network File System (NFS) that supports access to files larger than 4GB and increases sequential write throughput sevenfold when compared to unaccelerated NFS Version 2. NFS Version 3 maintains the stateless server design and simple crash recovery of NFS Version 2, and the philosophy of building a distributed file service from cooperating protocols. We describe the protocol and its implementation, and provide initial performance measurements. We then describe the implementation effort. Finally, we contrast this work with other distributed file systems and discuss future revisions of NFS. 1.
Microsystems
, 1993
"... this document is to: . Specify the NFS version 3 protocol . Describe semantics of the protocol through annotation and description of intended implementation . Specify the MOUNT version 3 protocol . Briefly describe the changes between the NLM version 3 protocol and the NLM version 4 protocol. The no ..."
Abstract
- Add to MetaCart
this document is to: . Specify the NFS version 3 protocol . Describe semantics of the protocol through annotation and description of intended implementation . Specify the MOUNT version 3 protocol . Briefly describe the changes between the NLM version 3 protocol and the NLM version 4 protocol. The normative text is the description of the RPC procedures and arguments and results, which defines the over-thewire protocol, and the semantics of those procedures. The material describing implementation practice aids the understanding of the protocol specification and describes some possible implementation issues and solutions. It is not possible to describe all implementations and the UNIX

