Network File System: Difference between revisions

Revision as of 18:48, 15 November 2024

Revision as of 00:52, 23 December 2024

Line 26:

The first NFS Version&nbsp;3 proposal within Sun Microsystems was created not long after the release of NFS Version&nbsp;2. The principal motivation was an attempt to mitigate the performance issue of the synchronous write operation in NFS Version&nbsp;2.<ref name="usenix94">{{cite web |url= https://www.usenix.org/legacy/publications/library/proceedings/bos94/full_papers/pawlowski.ps |title=NFS Version&nbsp;3 Design and Implementation |year=1994 |publisher=[[USENIX]] |author1=Brian Pawlowski |author2=Chet Juszczak |author3=Peter Staubach |author4=Carl Smith |author5=Diane Lebel |author6=David Hitz }}</ref> By July 1992, implementation practice had solved many shortcomings of NFS Version&nbsp;2, leaving only lack of large file support (64-bit file sizes and offsets) a pressing issue. At the time of introduction of Version&nbsp;3, vendor support for [[Transmission Control Protocol|TCP]] as a [[transport layer|transport-layer]] protocol began increasing. While several vendors had already added support for NFS Version&nbsp;2 with TCP as a transport, Sun Microsystems added support for TCP as a transport for NFS at the same time it added support for Version&nbsp;3. Using TCP as a transport made using NFS over a [[Wide area network|WAN]] more feasible, and allowed the use of larger read and write transfer sizes beyond the 8&nbsp;KB limit imposed by [[User Datagram Protocol]].

====YANFS/WebNFS====

{{anchor|WebNFS|reason=Old section name; could have incoming links, though they should probably go to the main article.}}

{{Main|WebNFS}}

YANFS (Yet Another NFS), formerly [[WebNFS]], wasis an extension to NFSv2 and NFSv3 allowing it to function behind restrictive firewalls without the complexity of Portmap and MOUNT protocols. YANFS/WebNFS hadhas a fixed [[List of TCP and UDP port numbers|TCP/UDP port number]] (2049), and instead of requiring the client to contact the MOUNT RPC service to determine the initial filehandle of every filesystem, it introduced the concept of a ''public filehandle'' (null for NFSv2, zero-length for NFSv3) which could be used as the starting point. Both of those changes havewere later been incorporated into NFSv4. YANFS's post-WebNFS development has also included server-side integration.

===NFSv4===