# Network File System

> Mediated Wiki article. Canonical URL: https://mediated.wiki/source/Network_File_System
> Markdown URL: https://mediated.wiki/source/Network_File_System.md
> Source: https://en.wikipedia.org/wiki/Network_File_System
> Source revision: 1354153623
> License: Creative Commons Attribution-ShareAlike 4.0 International (https://creativecommons.org/licenses/by-sa/4.0/)

Distributed file system protocol

Not to be confused with [NTFS](/source/NTFS).

This article is about a specific protocol. For the general concept, see [distributed file system](/source/Distributed_file_system).

Internet protocol suite Application layer BGP DHCP (v6) DNS FTP HTTP (HTTP/3) HTTPS IMAP IPP IRC LDAP MGCP MQTT NNTP NTP OSPF POP PTP ONC/RPC RTP RTSP RIP SIP SMTP SNMP SSH Telnet TLS/SSL XMPP more... Transport layer TCP UDP DCCP SCTP RSVP QUIC more... Internet layer IP v4 v6 ICMP (v6) NDP ECN L4S IGMP IPsec more... Link layer ARP Tunnels PPP MAC more... v t e

**Network File System** (**NFS**) is a [distributed file system](/source/Distributed_file_system) protocol originally developed by [Sun Microsystems](/source/Sun_Microsystems) (Sun) in 1984,[1] allowing a user on a client [computer](/source/Computer) to access files over a [computer network](/source/Computer_network) much like local storage is accessed. NFS, like many other protocols, builds on the [Open Network Computing Remote Procedure Call](/source/Open_Network_Computing_Remote_Procedure_Call) (ONC RPC) system. NFS is an open [IETF](/source/IETF) standard. After the first experimental version developed in house at Sun Microsystems, all subsequent versions of the protocol are defined in a series of [Request for Comments](/source/Request_for_Comments) i.e. RFCs, allowing anyone to implement the protocol.

## Versions and variations

Sun used version 1 only for in-house experimental purposes. When the development team added substantial changes to NFS version 1 and released it outside of Sun, they decided to release the new version as v2, so that version interoperation and RPC version fallback could be tested.[2][3]

### NFSv2

Version 2 of the protocol (defined in RFC [1094](https://www.rfc-editor.org/rfc/rfc1094), March 1989) originally operated only over [User Datagram Protocol](/source/User_Datagram_Protocol) (UDP). Its designers meant to keep the server side [stateless](/source/Stateless_server), with [locking](/source/Lock_(computer_science)) (for example) implemented outside of the core protocol. People involved in the creation of NFS version 2 include [Russel Sandberg](https://en.wikipedia.org/w/index.php?title=Russel_Sandberg&action=edit&redlink=1), [Bob Lyon](https://en.wikipedia.org/w/index.php?title=Bob_Lyon_(engineer)&action=edit&redlink=1), [Bill Joy](/source/Bill_Joy), [Steve Kleiman](https://en.wikipedia.org/w/index.php?title=Steve_Kleiman&action=edit&redlink=1), and others.[1][4]

The [Virtual File System](/source/Virtual_File_System) interface allows a modular implementation, reflected in a simple protocol. By February 1986, implementations were demonstrated for operating systems such as [System V](/source/System_V) release 2, [DOS](/source/DOS), and VAX/VMS using [Eunice](/source/Eunice_(software)).[4] NFSv2 only allows the first 2 GB of a file to be read due to [32-bit](/source/32-bit) limitations.

### NFSv3

Version 3 (RFC [1813](https://www.rfc-editor.org/rfc/rfc1813), June 1995) added:

- support for 64-bit file sizes and offsets, to handle files larger than 2 gigabytes (GB);

- support for asynchronous writes on the server, to improve write performance;

- additional file attributes in many replies, to avoid the need to re-fetch them;

- a READDIRPLUS operation, to get file handles[5] and attributes along with file names when scanning a directory;

- assorted other improvements.

The first NFS Version 3 proposal within Sun Microsystems was created not long after the release of NFS Version 2. The principal motivation was an attempt to mitigate the performance issue of the synchronous write operation in NFS Version 2.[6] By July 1992, implementation practice had solved many shortcomings of NFS Version 2, leaving only lack of large file support (64-bit file sizes and offsets) a pressing issue. At the time of introduction of Version 3, vendor support for [TCP](/source/Transmission_Control_Protocol) as a [transport-layer](/source/Transport_layer) protocol began increasing. While several vendors had already added support for NFS Version 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 3. Using TCP as a transport made using NFS over a [WAN](/source/Wide_area_network) more feasible, and allowed the use of larger read and write transfer sizes beyond the 8 KB limit imposed by [User Datagram Protocol](/source/User_Datagram_Protocol).

#### YANFS/WebNFS

Main article: [WebNFS](/source/WebNFS)

YANFS (Yet Another NFS), formerly WebNFS, is an extension to NFSv2 and NFSv3 allowing it to function behind restrictive firewalls without the complexity of Portmap and MOUNT protocols. YANFS/WebNFS has a fixed [TCP/UDP port number](/source/List_of_TCP_and_UDP_port_numbers) (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 were later incorporated into NFSv4. YANFS's post-WebNFS development has also included server-side integration.

### NFSv4

Version 4 (RFC [3010](https://www.rfc-editor.org/rfc/rfc3010), December 2000; revised in RFC [3530](https://www.rfc-editor.org/rfc/rfc3530), April 2003 and again in RFC [7530](https://www.rfc-editor.org/rfc/rfc7530), March 2015), influenced by [Andrew File System](/source/Andrew_File_System) (AFS) and [Server Message Block](/source/Server_Message_Block) (SMB), includes performance improvements, mandates strong security, and introduces a [stateful](/source/State_(computer_science)) protocol.[7][8] Version 4 became the first version developed with the [Internet Engineering Task Force](/source/Internet_Engineering_Task_Force) (IETF) after [Sun Microsystems](/source/Sun_Microsystems) handed over the development of the NFS protocols.

NFS version **4.1** (RFC [5661](https://www.rfc-editor.org/rfc/rfc5661), January 2010; revised in RFC [8881](https://www.rfc-editor.org/rfc/rfc8881), August 2020) aims to provide protocol support to take advantage of clustered server deployments including the ability to provide scalable parallel access to files distributed among multiple servers (**pNFS** extension). Version 4.1 includes Session trunking mechanism (Also known as NFS Multipathing) and is available in some enterprise solutions as [VMware ESXi](/source/VMware_ESXi).

NFS version **4.2** (RFC [7862](https://www.rfc-editor.org/rfc/rfc7862)) was published in November 2016 with new features including: server-side clone and copy, application I/O advise, sparse files, space reservation, application data block (ADB), labeled NFS with sec_label that accommodates any MAC security system, and two new operations for pNFS (LAYOUTERROR and LAYOUTSTATS).

One big advantage of NFSv4 over its predecessors is that only one UDP or TCP port, 2049, is used to run the service, which simplifies using the protocol across firewalls.[9]

### Other extensions

[WebNFS](/source/WebNFS), an extension to Version 2 and Version 3, allows NFS to integrate more easily into Web-browsers and to enable operation through firewalls. In 2007 Sun Microsystems open-sourced their client-side WebNFS implementation.[10]

Various side-band protocols have become associated with NFS. Note:

- the byte-range advisory Network Lock Manager (NLM) protocol (added to support [UNIX System V](/source/UNIX_System_V) [file locking](/source/File_locking) APIs)

- the remote quota-reporting (RQUOTAD) protocol, which allows NFS users to view their data-storage quotas on NFS servers

- NFS over RDMA, an adaptation of NFS that uses [remote direct memory access](/source/Remote_direct_memory_access) (RDMA) as a transport[11][12]

- NFS-Ganesha, an NFS server, running in user-space and supporting various file systems like [GPFS/Spectrum Scale](/source/GPFS), CephFS via respective FSAL (File System Abstraction Layer) modules. The [CephFS](/source/Ceph_(software)) FSAL is supported using libcephfs[13]

- Trusted NFS (TNFS)[14]

## Protocol development

During the development of the ONC protocol (called [SunRPC](/source/SunRPC) at the time), only Apollo's [Network Computing System](/source/Network_Computing_System) (NCS) offered comparable functionality. Two competing groups developed over fundamental differences in the two remote procedure call systems. Arguments focused on the method for data-encoding — ONC's [External Data Representation](/source/External_Data_Representation) (XDR) always rendered integers in [big-endian](/source/Big-endian) order, even if both peers of the connection had [little-endian](/source/Little-endian) machine-architectures, whereas NCS's method attempted to avoid byte-swap whenever two peers shared a common [endianness](/source/Endianness) in their machine-architectures. An industry-group called the [Network Computing Forum](https://en.wikipedia.org/w/index.php?title=Network_Computing_Forum&action=edit&redlink=1) formed (March 1987) in an (ultimately unsuccessful) attempt to reconcile the two network-computing environments.

In 1987, Sun and AT&T announced they would jointly develop AT&T's UNIX System V Release 4.[15] This caused many of AT&T's other licensees of UNIX System to become concerned that this would put Sun in an advantaged position, and ultimately led to Digital Equipment, HP, IBM, and others forming the [Open Software Foundation](/source/Open_Software_Foundation) (OSF) in 1988. Ironically, Sun and AT&T had formerly competed over Sun's NFS versus AT&T's [Remote File System](/source/Remote_File_System) (RFS), and the quick adoption of NFS over RFS by Digital Equipment, HP, IBM, and many other computer vendors tipped the majority of users in favor of NFS. NFS [interoperability](/source/Interoperability) was aided by events called "Connectathons" starting in 1986 that allowed vendor-neutral testing of implementations with each other.[16] OSF adopted the [Distributed Computing Environment](/source/Distributed_Computing_Environment) (DCE) and the [DCE Distributed File System](/source/DCE_Distributed_File_System) (DFS) over Sun/ONC RPC and NFS. DFS used DCE as the RPC, and DFS derived from the [Andrew File System](/source/Andrew_File_System) (AFS); DCE itself derived from a suite of technologies, including Apollo's NCS and [Kerberos](/source/Kerberos_(protocol)).[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

### 1990s

Sun Microsystems and the [Internet Society](/source/Internet_Society) (ISOC) reached an agreement to cede "change control" of ONC RPC so that the ISOC's engineering-standards body, the [Internet Engineering Task Force](/source/Internet_Engineering_Task_Force) (IETF), could publish standards documents (RFCs) related to ONC RPC protocols and could extend ONC RPC. OSF attempted to make DCE RPC an IETF standard, but ultimately proved unwilling to give up change control. Later, the IETF chose to extend ONC RPC by adding a new authentication flavor based on [Generic Security Services Application Program Interface](/source/Generic_Security_Services_Application_Program_Interface) (GSSAPI), [RPCSEC GSS](https://en.wikipedia.org/w/index.php?title=RPCSEC_GSS&action=edit&redlink=1), to meet IETF requirements that protocol standards have adequate security.

Later, Sun and ISOC reached a similar agreement to give ISOC change control over NFS, although writing the contract carefully to exclude NFS version 2 and version 3. Instead, ISOC gained the right to add new versions to the NFS protocol, which resulted in IETF specifying NFS version 4 in 2003.

### 2000s

By the 21st century, neither DFS nor AFS had achieved any major commercial success as compared to SMB or NFS. IBM, which had formerly acquired the primary commercial vendor of DFS and AFS, [Transarc](/source/Transarc), donated most of the AFS source code to the [free software community](/source/Free_software_community) in 2000. The [OpenAFS](/source/OpenAFS) project lives on. In early 2005, IBM announced end of sales for AFS and DFS.

In January, 2010, [Panasas](/source/Panasas) proposed an NFSv4.1 based on their *Parallel NFS* (pNFS) technology claiming to improve data-access parallelism[17] capability. The NFSv4.1 protocol defines a method of separating the [filesystem meta-data](/source/Metadata#File_system_metadata) from file data location; it goes beyond the simple name/data separation by striping the data amongst a set of data servers. This differs from the traditional NFS server which holds the names of files and their data under the single umbrella of the server. Some products are multi-node NFS servers, but the participation of the client in separation of meta-data and data is limited.

The NFSv4.1 pNFS server is a set of server resources or components; these are assumed to be controlled by the meta-data server.

The pNFS client still accesses one meta-data server for traversal or interaction with the namespace; when the client moves data to and from the server it may directly interact with the set of data servers belonging to the pNFS server collection. The NFSv4.1 client can be enabled to be a direct participant in the exact location of file data and to avoid solitary interaction with one NFS server when moving data.

In addition to pNFS, NFSv4.1 provides:

- Sessions

- Directory Delegation and Notifications

- Multi-server Namespace

- [access control lists](/source/Access_control_list) and [discretionary access control](/source/Discretionary_access_control)

- Retention Attributions

- SECINFO_NO_NAME

## Platforms

NFS is available on:

- [Unix-like](/source/Unix-like) operating systems ([Solaris](/source/Solaris_(operating_system)), [AIX](/source/AIX), [HP-UX](/source/HP-UX), [FreeBSD](/source/FreeBSD), [NetBSD](/source/NetBSD), [OpenBSD](/source/OpenBSD), [DragonFly BSD](/source/DragonFly_BSD), [Linux distributions](/source/Linux_distributions), and [macOS](/source/MacOS),[18] although the default networking protocol in macOS is [Server Message Block](/source/Server_Message_Block) (SMB)[19])

- [AmigaOS](/source/AmigaOS)

- [ArcaOS](/source/ArcaOS)[20]

- [Haiku](/source/Haiku_(operating_system))[21]

- [IBM i](/source/IBM_i),[22] although the default networking protocol is OS/400 File Server (QFileSvr.400)

- [Microsoft Windows](/source/Microsoft_Windows),[23] although the default networking protocol is [Server Message Block](/source/Server_Message_Block) (SMB)

- [MS-DOS](/source/MS-DOS)[24]

- [Novell NetWare](/source/Novell_NetWare),[25] although the default networking protocol is [NetWare Core Protocol](/source/NetWare_Core_Protocol) (NCP)

- [OpenVMS](/source/OpenVMS)[3]

- [OS/2](/source/OS%2F2)[26]

- [RISC OS](/source/RISC_OS)[27]

NFS SPECsfs2008 performance comparison, as of 22 November 2013

## See also

- [9P (protocol)](/source/9P_(protocol))

- [Alluxio](/source/Alluxio)

- [BeeGFS](/source/BeeGFS)

- [CacheFS](/source/CacheFS) – a caching mechanism for Linux NFS clients

- [Hadoop Distributed File System](/source/Hadoop_Distributed_File_System) (HDFS)

- [Kerberos (protocol)](/source/Kerberos_(protocol))

- [Network Information Service](/source/Network_Information_Service)

- [Remote File System](/source/Remote_File_System)

- [Root squash](/source/Root_squash)

- [Secure Shell Filesystem](/source/Secure_Shell_Filesystem)

- [Shared resource](/source/Shared_resource)

- [TCP Wrapper](/source/TCP_Wrapper)

## References

1. ^ [***a***](#cite_ref-sun85_1-0) [***b***](#cite_ref-sun85_1-1) Russel Sandberg; David Goldberg; Steve Kleiman; Dan Walsh; Bob Lyon (June 11–14, 1985). [*Design and Implementation of the Sun Network Filesystem*](https://www.cs.cornell.edu/courses/cs6411/2018sp/papers/nfs.pdf) (PDF). Usenix Association Summer Conference. Portland, Oregon USA. [CiteSeerX](/source/CiteSeerX_(identifier)) [10.1.1.14.473](https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.14.473).

1. **[^](#cite_ref-2)** *NFS Illustrated* (2000) by Brent Callaghan – [ISBN](/source/ISBN_(identifier)) [0-201-32570-5](https://en.wikipedia.org/wiki/Special:BookSources/0-201-32570-5)

1. ^ [***a***](#cite_ref-NFSforVMS_3-0) [***b***](#cite_ref-NFSforVMS_3-1) ["HP TCP/IP Services for OpenVMS Management"](https://web.archive.org/web/20160924192510/http://h41379.www4.hpe.com/doc/83final/6526/6526pro_052.html). *h41379.www4.hpe.com*. HP. Archived from [the original](http://h41379.www4.hpe.com/doc/83final/6526/6526pro_052.html) on 2016-09-24. Retrieved 24 September 2016.

1. ^ [***a***](#cite_ref-Rusty_4-0) [***b***](#cite_ref-Rusty_4-1) Russel Sandberg. ["The Sun Network Filesystem: Design, Implementation and Experience"](http://www.cse.buffalo.edu/faculty/tkosar/cse710_spring13/papers/nfs.pdf) (PDF). *Technical Report*. Sun Microsystems. [Archived](https://web.archive.org/web/20131126095851/http://www.cse.buffalo.edu/faculty/tkosar/cse710_spring13/papers/nfs.pdf) (PDF) from the original on 2013-11-26. Retrieved 2013-08-04.

1. **[^](#cite_ref-5)** Arpaci-Dusseau, Remzi; Arpaci-Dusseau, Andrea (March 2015). [*Operating Systems: Three Easy Pieces*](http://pages.cs.wisc.edu/~remzi/OSTEP/dist-nfs.pdf) (PDF) (.9 ed.). Arpaci-Dusseau Books. p. 5. [Archived](https://web.archive.org/web/20190403140732/http://pages.cs.wisc.edu/~remzi/OSTEP/dist-nfs.pdf) (PDF) from the original on 3 April 2019. Retrieved 8 November 2017.

1. **[^](#cite_ref-usenix94_6-0)** Brian Pawlowski; Chet Juszczak; Peter Staubach; Carl Smith; Diane Lebel; David Hitz (1994). ["NFS Version 3 Design and Implementation"](https://www.usenix.org/legacy/publications/library/proceedings/bos94/full_papers/pawlowski.ps). [USENIX](/source/USENIX). [Archived](https://web.archive.org/web/20151124182558/https://www.usenix.org/legacy/publications/library/proceedings/bos94/full_papers/pawlowski.ps) from the original on 2015-11-24. Retrieved 2015-11-23.

1. **[^](#cite_ref-7)** ["NFS Version 4"](http://www.usenix.org/events/usenix05/tech/italks.html#nFSv4). [USENIX](/source/USENIX). 2005-04-14. [Archived](https://web.archive.org/web/20110728150342/http://www.usenix.org/events/usenix05/tech/italks.html#nFSv4) from the original on 2011-07-28. Retrieved 2008-12-19.

1. **[^](#cite_ref-sane2000_8-0)** Brian Pawlowski; Spencer Shepler; Carl Beame; Brent Callaghan; Michael Eisler; David Noveck; David Robinson; Robert Thurlow (2000). ["The NFS Version 4 Protocol"](https://web.archive.org/web/20250202030621/http://www.sane.nl/events/sane2000/papers/pawlowski.pdf) (PDF). [SANE](https://en.wikipedia.org/w/index.php?title=System_Administration_and_Network_Engineering&action=edit&redlink=1). Archived from [the original](http://www.sane.nl/events/sane2000/papers/pawlowski.pdf) (PDF) on 2025-02-02.

1. **[^](#cite_ref-9)** Justin Parisi; Elliott Ecton (June 2023). [*NFS in NetApp ONTAP, Best practice and implementation guide*](https://www.netapp.com/media/10720-tr-4067.pdf) (PDF) (Technical report). NetApp.

1. **[^](#cite_ref-10)** ["yanfs"](https://github.com/raisercostin/yanfs). *Github.com*.

1. **[^](#cite_ref-11)** Tom Talpey (February 28, 2006). ["NFS/RDMA Implementation(s) Update"](https://web.archive.org/web/20110512180716/http://www.connectathon.org/talks06/talpey-cthon06-nfs-rdma.pdf) (PDF). Network Appliance, Inc. Archived from [the original](http://www.connectathon.org/talks06/talpey-cthon06-nfs-rdma.pdf) (PDF) on May 12, 2011.

1. **[^](#cite_ref-12)** Brent Callaghan (January 28, 2002). ["NFS over RDMA"](http://www.usenix.org/events/fast02/wips/callaghan.pdf) (PDF). Sun Microsystems. [Archived](https://web.archive.org/web/20110512180713/http://www.usenix.org/events/fast02/wips/callaghan.pdf) (PDF) from the original on May 12, 2011. Retrieved September 6, 2010.

1. **[^](#cite_ref-13)** Singh, Karan (2016). "4: Working with the Ceph Filesystem". [*Ceph Cookbook*](https://books.google.com/books?id=C2xLDAAAQBAJ). Birmingham: Packt Publishing Ltd. p. 110. [ISBN](/source/ISBN_(identifier)) [978-1-78439-736-4](https://en.wikipedia.org/wiki/Special:BookSources/978-1-78439-736-4). Retrieved 2017-03-21. NFS-Ganesha is an NFS server that runs in user space and supports the CephFS FSAL (File System Abstraction Layer) using libcephfs.

1. **[^](#cite_ref-14)** Glover, Fred (28 May 1994). ["A Specification of Trusted NFS (TNFS) Protocol Extensions"](https://tools.ietf.org/html/draft-ietf-tnfs-spec-01.html). *datatracker.ietf.org*.

1. **[^](#cite_ref-15)** Carole Patton (1987-10-26). ["AT&T to License Sun Microsystems' SPARC Chip"](https://books.google.com/books?id=_z4EAAAAMBAJ&pg=PA37). *[InfoWorld](/source/InfoWorld)*. p. 37. Retrieved 2019-07-16.

1. **[^](#cite_ref-16)** ["What is Connectathon?"](https://web.archive.org/web/19990128152940/http://www.connectathon.org/#whatis). *Original Connectathon.Org web site*. Archived from [the original](http://www.connectathon.org/) on January 28, 1999.

1. **[^](#cite_ref-17)** ["pNFS"](http://www.pnfs.com/). [Panasas](/source/Panasas). [Archived](https://web.archive.org/web/20130807180615/http://www.pnfs.com/) from the original on August 7, 2013. Retrieved August 4, 2013.

1. **[^](#cite_ref-18)** ["Servers and shared computers you can connect to on Mac"](https://support.apple.com/guide/mac-help/servers-shared-computers-connect-mac-mchlp3015/15.0/mac/15.0). *Apple Support*. Retrieved 7 August 2025.

1. **[^](#cite_ref-19)** ["Set up file sharing on Mac"](https://support.apple.com/guide/mac-help/set-up-file-sharing-on-mac-mh17131/15.0/mac/15.0). *Apple Support*. Retrieved 7 August 2025.

1. **[^](#cite_ref-20)** ["NetDrive for OS/2"](https://www.arcanoae.com/shop/netdrive-for-os2/). *arcanoae.com*. [Archived](https://web.archive.org/web/20151103233414/https://www.arcanoae.com/shop/netdrive-for-os2/) from the original on 2015-11-03. Retrieved 2020-09-22.

1. **[^](#cite_ref-21)** Dziepak, Paweł (2013-03-15). ["NFSv4 client finally merged"](https://www.haiku-os.org/blog/pawe%C5%82_dziepak/2013-03-15_nfsv4_client_finally_merged/). *Paweł Dziepak's blog*. Haiku, Inc.

1. **[^](#cite_ref-OS/400-NFS_22-0)** ["OS/400 Network File System Support"](https://public.dhe.ibm.com/systems/power/docs/systemi/v5r4/en_US/sc415714.pdf) (PDF). IBM. Retrieved 23 May 2024.

1. **[^](#cite_ref-SFU_23-0)** ["Introduction to Microsoft Windows Services for UNIX 3.5"](https://technet.microsoft.com/en-us/library/bb463212.aspx). *technet.microsoft.com*. Microsoft. 5 December 2007. [Archived](https://web.archive.org/web/20180618045332/https://technet.microsoft.com/en-us/library/bb463212.aspx) from the original on 18 June 2018. Retrieved 24 September 2016.

1. **[^](#cite_ref-PCNFS_24-0)** ["Other Software by SUN Microsystems"](http://www.computinghistory.org.uk/det/12549/PC-NFS%20version%205.0/). *www.computinghistory.org.uk*. The Centre for Computing History. Retrieved 24 September 2016.

1. **[^](#cite_ref-NFSforNetWare_25-0)** ["NFS Gateway for NetWare 6.5"](https://www.novell.com/products/openenterpriseserver/features/nfs-gateway-for-netware65.html). *www.novell.com*. Novell. Retrieved 24 September 2016.

1. **[^](#cite_ref-26)** ["NTFS plugin for NetDrive"](https://ecsoft2.org/network-file-system-nfs-plugin-netdrive). *ecsoft2.org*. [Archived](https://web.archive.org/web/20160222155213/https://ecsoft2.org/network-file-system-nfs-plugin-netdrive) from the original on 2016-02-22. Retrieved 2020-09-22.

1. **[^](#cite_ref-Sunfish/Moonfish_by_Alex_Waugh_27-0)** ["Networking related programs"](http://www.cp15.org/networking/). *cp15.org*.

## External links

- [RFCs](/source/Request_for_Comments): - RFC [1014](https://www.rfc-editor.org/rfc/rfc1014) – XDR: External Data Representation Standard (obsoleted by RFC 1832) - RFC [1094](https://www.rfc-editor.org/rfc/rfc1094) – NFS Version 2 Protocol Specification - RFC [1790](https://www.rfc-editor.org/rfc/rfc1790) – Sun/ISOC ONC RPC Change Control Agreement - RFC [1813](https://www.rfc-editor.org/rfc/rfc1813) – NFS Version 3 Protocol Specification - RFC [1832](https://www.rfc-editor.org/rfc/rfc1832) – XDR: External Data Representation Standard (obsoleted by RFC 4506) - RFC [2054](https://www.rfc-editor.org/rfc/rfc2054) – WebNFS Client Specification - RFC [2055](https://www.rfc-editor.org/rfc/rfc2055) – WebNFS Server Specification - RFC [2203](https://www.rfc-editor.org/rfc/rfc2203) – RPCSEC_GSS Specification - RFC [2224](https://www.rfc-editor.org/rfc/rfc2224) – NFS URL Scheme Specification - RFC [2339](https://www.rfc-editor.org/rfc/rfc2339) – Sun/ISOC NFS Change Control Agreement - RFC [3010](https://www.rfc-editor.org/rfc/rfc3010) – NFS Version 4 Protocol Specification (obsoleted by RFC 3530) - RFC [3530](https://www.rfc-editor.org/rfc/rfc3530) – NFS Version 4 Protocol Specification (obsoleted by RFC 7530 and RFC 7531) - RFC [4506](https://www.rfc-editor.org/rfc/rfc4506) – XDR: External Data Representation Standard - RFC [5403](https://www.rfc-editor.org/rfc/rfc5403) – RPCSEC_GSS Version 2 - RFC [5531](https://www.rfc-editor.org/rfc/rfc5531) – RPC: Remote Procedure Call Protocol Specification Version 2 - RFC [5661](https://www.rfc-editor.org/rfc/rfc5661) – NFS Version 4.1 Protocol Specification (obsoleted by RFC 8881) - RFC [5662](https://www.rfc-editor.org/rfc/rfc5662) – NFS Version 4.1 Protocol XDR Description - RFC [5663](https://www.rfc-editor.org/rfc/rfc5663) – Parallel NFS - Block/Volume Layout Specification - RFC [5664](https://www.rfc-editor.org/rfc/rfc5664) – Parallel NFS - Object-Based Operations Specification - RFC [5665](https://www.rfc-editor.org/rfc/rfc5665) – IANA Considerations for Remote Procedure Call (RPC) Network Identifiers and Universal Address Formats - RFC [5666](https://www.rfc-editor.org/rfc/rfc5666) – Remote Direct Memory Access Transport for Remote Procedure Call - RFC [5667](https://www.rfc-editor.org/rfc/rfc5667) – NFS Direct Data Placement - RFC [7530](https://www.rfc-editor.org/rfc/rfc7530) – NFS Version 4 Protocol Specification - RFC [7531](https://www.rfc-editor.org/rfc/rfc7531) – NFS Version 4 Protocol XDR Description - RFC [7862](https://www.rfc-editor.org/rfc/rfc7862) – NFS Version 4.2 Protocol Specification - RFC [7863](https://www.rfc-editor.org/rfc/rfc7863) – NFS Version 4.2 Protocol XDR Description - RFC [8154](https://www.rfc-editor.org/rfc/rfc8154) – Parallel NFS - SCSI Layout Specification - RFC [8166](https://www.rfc-editor.org/rfc/rfc8166) – Remote Direct Memory Access Transport for Remote Procedure Call Version 1 (updated by RFC 8797) - RFC [8267](https://www.rfc-editor.org/rfc/rfc8267) – NFS Upper-Layer Binding to RPC-over-RDMA Version 1 - RFC [8275](https://www.rfc-editor.org/rfc/rfc8275) – Umask attribute extension for NFS Version 4.2 - RFC [8276](https://www.rfc-editor.org/rfc/rfc8276) – Xattrs extension for NFSv4 - RFC [8434](https://www.rfc-editor.org/rfc/rfc8434) – Parallel NFS - Flexible File Layout Specification - RFC [8797](https://www.rfc-editor.org/rfc/rfc8797) – Remote Direct Memory Access - Connection Manager (RDMA-CM) Private Data for RPC-over-RDMA Version 1 - RFC [8881](https://www.rfc-editor.org/rfc/rfc8881) – NFS Version 4.1 Protocol Specification - RFC [9289](https://www.rfc-editor.org/rfc/rfc9289) – Towards Remote Procedure Call Encryption by Default - RFC [9562](https://www.rfc-editor.org/rfc/rfc9562) – Universally Unique IDentifiers (UUIDs)

- Open Group Technical Standards: - [Protocols for Interworking: XNFS, Version 3W](https://archive.opengroup.org/publications/archive/CDROM/c702.pdf) – Open Group specification of NFS2, NFS3 and side-band protocols MNT, NSM and NLM for file locking which are not covered by RFC documents - [Protocols for X/Open PC Interworking: (PC)NFS](https://archive.opengroup.org/publications/archive/CDROM/d030.pdf) – Open Group specification of NFS2 and side-band protocols MNT, NLM and PCNFSD which are not covered by RFC documents

- Various resources: - [Network File System (NFS) 2.0 implementation](https://www.tuhs.org/Archive/Distributions/Sun/) - [IETF: Network File System Version 4 (nfsv4) Charter](https://web.archive.org/web/20080216083308/http://www.ietf.org/html.charters/nfsv4-charter.html) - [Linux NFS Overview, FAQ and HOWTO Documents](http://linux-nfs.org/wiki/index.php/Main_Page) - [NFS operation explained with sequence diagrams](http://www.eventhelix.com/RealtimeMantra/Networking/NFS_Protocol_Sequence_Diagram.pdf) [Archived](https://web.archive.org/web/20200922193017/http://www.eventhelix.com/RealtimeMantra/Networking/NFS_Protocol_Sequence_Diagram.pdf) 2020-09-22 at the [Wayback Machine](/source/Wayback_Machine)

- [Review of "Why NFS Sucks" Paper from the 2006 Linux Symposium](http://nfsworld.blogspot.com/2006/10/review-of-why-nfs-sucks-paper-from.html) by Mike Eisler, October 27, 2006

v t e Uniform Resource Identifier (URI) schemes Official about acct crid data file ftp geo gopher http https info ldap mailto nfs nntp sip / sips tag telnet urn view-source ws / wss xmpp Unofficial coffee ed2k gemini feed finger irc / irc6 / ircs ldaps magnet rsync ymsgr Protocol list

v t e Sun Microsystems Acquired by Oracle Corporation Hardware Systems SUN workstation Sun-1 Sun-2 Sun-3 Sun386i Sun-4 SPARCstation–server–center 1 2 4 5 10 20 classic IPC IPX LX ZX Netra Ultra 1 2 5 10 24 30 60 80 Enterprise 10000 Blade server Blade workstation Fire 12K 15K E25K T2000 X4500 SPARC Enterprise JavaStation Java Workstation Ray Cobalt Qube Cobalt RaQ Processors SPARC MB86900 microSPARC SuperSPARC UltraSPARC UltraSPARC II UltraSPARC IIe UltraSPARC IIi Gemini UltraSPARC III UltraSPARC III Cu UltraSPARC IIIi UltraSPARC IV UltraSPARC T1 UltraSPARC T2 SPARC T3 SPARC T4 SPARC T5 Rock MAJC Sun4d SBus Fireplane LOM port MBus Modular Datacenter Neptune System Service Processor SPARC T series SPOT Ultra Port Architecture Visual Instruction Set Software TOPS SunOS Solaris NIS NIS+ NFS ZFS ZFS+ SunView NeWS OpenWindows Java Desktop System Studio Java StarOffice iPlanet Java System Sun Secure Global Desktop MySQL xVM GlassFish VirtualBox Storage StorageTek 5800 System StorageTek SL8500 Open Storage QFS ZFS Performance Cloud Constellation System Visualization System Grid Engine Lustre Research Sun Microsystems Laboratories picoJava Fortress Project Looking Glass Education BlueJ Global Education & Learning Community SCPs Acquisitions Afara Websystems Cobalt Networks Gridware Lighthouse Design Montalvo Systems MySQL AB Pixo Procom Technology SavaJe StorageTek Tarantella Slogans The Network is the Computer Write once, run anywhere Community Common Development and Distribution License Java Community Process NetBeans OpenOffice.org OpenSolaris OpenSPARC OpenJDK Open Source University Meetup People Bill Joy Andy Bechtolsheim Scott McNealy Vinod Khosla Category

v t e File systems Comparison of file systems distributed Unix filesystem Disk and non-rotating ADFS AdvFS Amiga FFS Amiga OFS APFS AthFS bcachefs BFS Be File System Boot File System Byte File System (z/VM) Btrfs CVFS CXFS DFS EFS Encrypting File System Extent File System Episode ext ext2 ext3 ext4 FAT exFAT Files-11 Fossil GPFS HAMMER HAMMER2 HFS (Classic Mac OS) HFS (MVS) HFS+ HPFS HTFS JFS LFS MFS Macintosh File System TiVo Media File System MINIX NetWare File System Next3 NILFS NILFS2 NSS NTFS OneFS OpenZFS PFS QFS QNX4FS ReFS ReiserFS Reiser4 Reliance Reliance Nitro RFS SFS Shared File System (VM) Smart File System SNFS Soup (Apple) Tux3 UBIFS UFS/UFS2 soft updates WAPBL VxFS WAFL Xiafs XFS Xsan zFS (z/OS) ZFS (Sun) Optical disc HSF ISO 9660 ISO 13490 UDF Flash memory and SSD APFS FAT exFAT TFAT EROFS F2FS JFS NVFS host-side wear leveling CHFS JFFS JFFS2 LogFS NILFS NILFS2 YAFFS UBIFS Distributed parallel BeeGFS Ceph CXFS GFS2 Google File System OCFS2 OrangeFS PVFS QFS Xsan more... NAS 9P AFS (OpenAFS) AFP Coda DFS Google File System GPFS Lustre NCP NFS POHMELFS Hadoop SMB (CIFS) SSHFS more... Specialized Aufs AXFS Boot File System Compact Disc File System cramfs Davfs2 EROFS FTPFS FUSE Lnfs LTFS NOVA MVFS SquashFS UMSDOS OverlayFS UnionFS Pseudo configfs devfs debugfs kernfs procfs specfs sysfs tmpfs WinFS Encrypted eCryptfs EncFS EFS Rubberhose SSHFS ZFS Types Clustered Global Grid Self-certifying Flash Journaling Log-structured Object Record-oriented Semantic Steganographic Synthetic Versioning Features Case preservation Copy-on-write Data deduplication Data scrubbing Execute in place Extent File attribute Extended file attributes File change log Fork Inode Links Hard Symbolic Access control Access-control list Filesystem-level encryption Permissions Modes Sticky bit Interfaces File manager File system API Installable File System Virtual file system Lists Cryptographic Default Log-structured Layouts Master Boot Record GUID Partition Table Apple Partition Map

Authority control databases National United States Israel Other Yale LUX

---
Adapted from the Wikipedia article [Network File System](https://en.wikipedia.org/wiki/Network_File_System) by Wikipedia contributors ([contributor history](https://en.wikipedia.org/wiki/Network_File_System?action=history)). Available under [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/). Changes may have been made.