Network File System - Revision history

DigitalIceAge: added Category:1984 software using HotCat

2025-04-16T22:24:48Z

added Category:1984 software using HotCat

← Previous revision		Revision as of 22:24, 16 April 2025
Line 191:		Line 191:
	[[Category:Distributed file systems]]		[[Category:Distributed file systems]]
	[[Category:Network booting]]		[[Category:Network booting]]
			[[Category:1984 software]]

WikiWikiPhil: Sort list chronologically per MOS:SORTLIST

2025-01-23T13:02:19Z

Sort list chronologically per MOS:SORTLIST

@@ Line 143: / Line 143: @@
 {{colbegin}}
 * [[Request for Comments|RFCs]]:
 ** {{IETF RFC|1094|link=no}} – NFS Version 2 Protocol Specification
 * Open Group Technical Standards:
 ** [https://archive.opengroup.org/publications/archive/CDROM/c702.pdf Protocols for Interworking: XNFS, Version 3W] – Open Group specification of NFS2, NFS3 and side-band protocols MNT, NSM and NLM for file locking which are not covered by RFC documents

WikiWikiPhil: Use RFC link template where applicable

2025-01-23T13:00:33Z

Use RFC link template where applicable

← Previous revision		Revision as of 13:00, 23 January 2025
Line 11:		Line 11:
	===NFSv2===		===NFSv2===

	Version 2 of the protocol (defined in ~~RFC~~ 1094, March 1989) originally operated only over [[User Datagram Protocol]] (UDP). Its designers meant to keep the server side [[Stateless server\|stateless]], with [[lock (computer science)\|locking]] (for example) implemented outside of the core protocol. People involved in the creation of NFS version 2 include [[Russel Sandberg]], [[Bob Lyon (engineer)\|Bob Lyon]], [[Bill Joy]], [[Steve Kleiman]], and others.<ref name="sun85" /><ref name="Rusty">{{Cite journal \|title= The Sun Network Filesystem: Design, Implementation and Experience \|journal= Technical Report \|author= Russel Sandberg \|publisher= Sun Microsystems \|url= http://www.cse.buffalo.edu/faculty/tkosar/cse710_spring13/papers/nfs.pdf }}</ref>		Version 2 of the protocol (defined in {{IETF RFC\|1094\|link=no}}, March 1989) originally operated only over [[User Datagram Protocol]] (UDP). Its designers meant to keep the server side [[Stateless server\|stateless]], with [[lock (computer science)\|locking]] (for example) implemented outside of the core protocol. People involved in the creation of NFS version 2 include [[Russel Sandberg]], [[Bob Lyon (engineer)\|Bob Lyon]], [[Bill Joy]], [[Steve Kleiman]], and others.<ref name="sun85" /><ref name="Rusty">{{Cite journal \|title= The Sun Network Filesystem: Design, Implementation and Experience \|journal= Technical Report \|author= Russel Sandberg \|publisher= Sun Microsystems \|url= http://www.cse.buffalo.edu/faculty/tkosar/cse710_spring13/papers/nfs.pdf }}</ref>

	The [[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]] release 2, [[DOS]], and VAX/VMS using [[Eunice (software)\|Eunice]].<ref name="Rusty" />		The [[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]] release 2, [[DOS]], and VAX/VMS using [[Eunice (software)\|Eunice]].<ref name="Rusty" />
Line 17:		Line 17:

	===NFSv3===		===NFSv3===
	Version 3 (~~RFC~~ 1813, June 1995) added:		Version 3 ({{IETF RFC\|1813\|link=no}}, June 1995) added:
	* support for 64-bit file sizes and offsets, to handle files larger than 2 gigabytes (GB);		* 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;		* support for asynchronous writes on the server, to improve write performance;
Line 32:		Line 32:

	===NFSv4===		===NFSv4===
	Version 4 (~~RFC~~ 3010, December 2000; revised in ~~RFC~~ 3530, April 2003 and again in ~~RFC~~ 7530, March 2015), influenced by [[Andrew File System]] (AFS) and [[Server Message Block]] (SMB), includes performance improvements, mandates strong security, and introduces a [[State (computer science)\|stateful]] protocol.<ref>{{cite web\|url=http://www.usenix.org/events/usenix05/tech/italks.html#nFSv4\|title=NFS Version 4\|date=2005-04-14\|publisher=[[USENIX]]}}</ref><ref name="sane2000">{{cite web \|url= http://www.sane.nl/events/sane2000/papers/pawlowski.pdf \|title=The NFS Version 4 Protocol \|year=2000 \|publisher=[[System Administration and Network Engineering\|SANE]] \|author1=Brian Pawlowski \|author2=Spencer Shepler \|author3=Carl Beame \|author4=Brent Callaghan \|author5=Michael Eisler \|author6=David Noveck \|author7=David Robinson \|author8=Robert Thurlow }}</ref> Version 4 became the first version developed with the [[Internet Engineering Task Force]] (IETF) after [[Sun Microsystems]] handed over the development of the NFS protocols.		Version 4 ({{IETF RFC\|3010\|link=no}}, December 2000; revised in {{IETF RFC\|3530\|link=no}}, April 2003 and again in {{IETF RFC\|7530\|link=no}}, March 2015), influenced by [[Andrew File System]] (AFS) and [[Server Message Block]] (SMB), includes performance improvements, mandates strong security, and introduces a [[State (computer science)\|stateful]] protocol.<ref>{{cite web\|url=http://www.usenix.org/events/usenix05/tech/italks.html#nFSv4\|title=NFS Version 4\|date=2005-04-14\|publisher=[[USENIX]]}}</ref><ref name="sane2000">{{cite web \|url= http://www.sane.nl/events/sane2000/papers/pawlowski.pdf \|title=The NFS Version 4 Protocol \|year=2000 \|publisher=[[System Administration and Network Engineering\|SANE]] \|author1=Brian Pawlowski \|author2=Spencer Shepler \|author3=Carl Beame \|author4=Brent Callaghan \|author5=Michael Eisler \|author6=David Noveck \|author7=David Robinson \|author8=Robert Thurlow }}</ref> Version 4 became the first version developed with the [[Internet Engineering Task Force]] (IETF) after [[Sun Microsystems]] handed over the development of the NFS protocols.

	NFS version 4.1 (~~RFC~~ 5661, January 2010; revised in ~~RFC~~ 8881, 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]].		NFS version 4.1 ({{IETF RFC\|5661\|link=no}}, January 2010; revised in {{IETF RFC\|8881\|link=no}}, 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]].

		⚫	NFS version 4.2 ({{IETF RFC\|7862\|link=no}}) 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).
	NFS version 4.2 (RFC 7862) was published in November 2016<ref>{{cite ietf
	\| url = https://tools.ietf.org/html/rfc7862
	\| title = NFS Version 4 Minor Version 2
	\| first = Thomas \| last = Haynes
	\| date = 2016-11-01
	\| doi = 10.17487/RFC7862
	\| doi-access = free
⚫	}}~~</ref>~~ 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.<ref>{{cite tech report\|url=https://www.netapp.com/media/10720-tr-4067.pdf\|title=NFS in NetApp ONTAP, Best practice and implementation guide\|author1=Justin Parisi\|author2= Elliott Ecton\|date=June 2023\|publisher=NetApp}}</ref>		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.<ref>{{cite tech report\|url=https://www.netapp.com/media/10720-tr-4067.pdf\|title=NFS in NetApp ONTAP, Best practice and implementation guide\|author1=Justin Parisi\|author2= Elliott Ecton\|date=June 2023\|publisher=NetApp}}</ref>

SMcCandlish: Update, and fix verb tense.

2024-12-23T00:52:36Z

Update, and fix verb tense.

← Previous revision		Revision as of 00:52, 23 December 2024
Line 26:		Line 26:
	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.<ref name="usenix94">{{cite web \|url= https://www.usenix.org/legacy/publications/library/proceedings/bos94/full_papers/pawlowski.ps \|title=NFS Version 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 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 [[Transmission Control Protocol\|TCP]] as a [[transport layer\|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 [[Wide area network\|WAN]] more feasible, and allowed the use of larger read and write transfer sizes beyond the 8 KB limit imposed by [[User Datagram Protocol]].		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.<ref name="usenix94">{{cite web \|url= https://www.usenix.org/legacy/publications/library/proceedings/bos94/full_papers/pawlowski.ps \|title=NFS Version 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 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 [[Transmission Control Protocol\|TCP]] as a [[transport layer\|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 [[Wide area network\|WAN]] more feasible, and allowed the use of larger read and write transfer sizes beyond the 8 KB limit imposed by [[User Datagram Protocol]].

	====WebNFS====		====YANFS/WebNFS====
			{{anchor\|WebNFS\|reason=Old section name; could have incoming links, though they should probably go to the main article.}}
	{{Main\|WebNFS}}		{{Main\|WebNFS}}
	[[WebNFS]] ~~was~~ an extension to NFSv2 and NFSv3 allowing it to function behind restrictive firewalls without the complexity of Portmap and MOUNT protocols. WebNFS ~~had~~ 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 ~~have~~ later ~~been~~ incorporated into NFSv4.		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 [[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 were later incorporated into NFSv4. YANFS's post-WebNFS development has also included server-side integration.

	===NFSv4===		===NFSv4===

178.40.48.120: /* External links */ Add reference to PCNFSD

2024-11-15T18:48:04Z

External links: Add reference to PCNFSD

← Previous revision		Revision as of 18:48, 15 November 2024
Line 175:		Line 175:
	* Open Group Technical Standards:		* Open Group Technical Standards:
	** [https://archive.opengroup.org/publications/archive/CDROM/c702.pdf Protocols for Interworking: XNFS, Version 3W] – Open Group specification of NFS2, NFS3 and side-band protocols MNT, NSM and NLM for file locking which are not covered by RFC documents		** [https://archive.opengroup.org/publications/archive/CDROM/c702.pdf Protocols for Interworking: XNFS, Version 3W] – Open Group specification of NFS2, NFS3 and side-band protocols MNT, NSM and NLM for file locking which are not covered by RFC documents
			** [https://archive.opengroup.org/publications/archive/CDROM/d030.pdf Protocols for X/Open PC Interworking: (PC)NFS] – Open Group specification of NFS2 and side-band protocols MNT, NLM and PCNFSD which are not covered by RFC documents
	* Various resources:		* Various resources:
	** [https://web.archive.org/web/20080216083308/http://www.ietf.org/html.charters/nfsv4-charter.html IETF: Network File System Version 4 (nfsv4) Charter]		** [https://web.archive.org/web/20080216083308/http://www.ietf.org/html.charters/nfsv4-charter.html IETF: Network File System Version 4 (nfsv4) Charter]

164.215.226.88: /* Platforms */ Added source for Haiku OS. Sorted the list alphabetically.

2024-10-22T06:36:54Z

Platforms: Added source for Haiku OS. Sorted the list alphabetically.

@@ Line 77: / Line 77: @@
 * [[Unix-like]] operating systems ([[Solaris (operating system)|Solaris]], [[AIX]], [[HP-UX]], [[FreeBSD]], and [[Linux distros]])
 * [[AmigaOS]]
 * [[ArcaOS]]<ref>{{cite web|url=https://www.arcanoae.com/shop/netdrive-for-os2/|title=NetDrive for OS/2|access-date=2020-09-22|website=arcanoae.com}}</ref>
 * [[IBM i]],<ref name="OS/400-NFS">{{cite web|title=OS/400 Network File System Support|url=https://public.dhe.ibm.com/systems/power/docs/systemi/v5r4/en_US/sc415714.pdf|publisher=IBM|access-date=23 May 2024}}</ref> although the default networking protocol is OS/400 File Server (QFileSvr.400)
 [[File:NfsPerformanceGraph.png|thumb|600px|center|NFS SPECsfs2008 performance comparison, as of 22 November 2013]]

164.215.226.88: /* See also */

2024-10-22T06:02:32Z

164.215.242.60: /* Typical implementation */ Deleted source-less section. It has been here for 15 years now. I don't know what it's trying to say anyway.

2024-10-21T21:22:52Z

Typical implementation: Deleted source-less section. It has been here for 15 years now. I don't know what it's trying to say anyway.

← Previous revision		Revision as of 21:22, 21 October 2024
Line 85:		Line 85:
	* [[OS/2]]<ref>{{cite web\|url=https://ecsoft2.org/network-file-system-nfs-plugin-netdrive\|access-date=2020-09-22\|website=ecsoft2.org\|title=NTFS plugin for NetDrive}}</ref>		* [[OS/2]]<ref>{{cite web\|url=https://ecsoft2.org/network-file-system-nfs-plugin-netdrive\|access-date=2020-09-22\|website=ecsoft2.org\|title=NTFS plugin for NetDrive}}</ref>
	* [[ArcaOS]]<ref>{{cite web\|url=https://www.arcanoae.com/shop/netdrive-for-os2/\|title=NetDrive for OS/2\|access-date=2020-09-22\|website=arcanoae.com}}</ref>		* [[ArcaOS]]<ref>{{cite web\|url=https://www.arcanoae.com/shop/netdrive-for-os2/\|title=NetDrive for OS/2\|access-date=2020-09-22\|website=arcanoae.com}}</ref>
	* [[Novell NetWare]],<ref name="NFSforNetWare">{{cite web\|title=NFS Gateway for NetWare 6.5\|url=https://www.novell.com/products/openenterpriseserver/features/nfs-gateway-for-netware65.html\|website=www.novell.com\|publisher=Novell\|access-date=24 September 2016}}</ref> although the ~~defult~~ networking protocol is [[NetWare Core Protocol]] (NCP)		* [[Novell NetWare]],<ref name="NFSforNetWare">{{cite web\|title=NFS Gateway for NetWare 6.5\|url=https://www.novell.com/products/openenterpriseserver/features/nfs-gateway-for-netware65.html\|website=www.novell.com\|publisher=Novell\|access-date=24 September 2016}}</ref> although the default networking protocol is [[NetWare Core Protocol]] (NCP)
	* [[IBM i]],<ref name="OS/400-NFS">{{cite web\|title=OS/400 Network File System Support\|url=https://public.dhe.ibm.com/systems/power/docs/systemi/v5r4/en_US/sc415714.pdf\|publisher=IBM\|access-date=23 May 2024}}</ref> although the default networking protocol is OS/400 File Server (QFileSvr.400)		* [[IBM i]],<ref name="OS/400-NFS">{{cite web\|title=OS/400 Network File System Support\|url=https://public.dhe.ibm.com/systems/power/docs/systemi/v5r4/en_US/sc415714.pdf\|publisher=IBM\|access-date=23 May 2024}}</ref> although the default networking protocol is OS/400 File Server (QFileSvr.400)

Line 91:		Line 91:

	[[File:NfsPerformanceGraph.png\|thumb\|600px\|center\|NFS SPECsfs2008 performance comparison, as of 22 November 2013]]		[[File:NfsPerformanceGraph.png\|thumb\|600px\|center\|NFS SPECsfs2008 performance comparison, as of 22 November 2013]]

	=== Typical implementation ===
	{{unreferenced section\|date=February 2010}}

	Assuming a Unix-style scenario in which one machine (the [[Client (computing)\|client]]) needs access to data stored on another machine (the NFS [[Server (computing)\|server]]):

	# The server implements NFS [[Daemon (computer software)\|daemon]] processes, running by default as <code>nfsd</code>, to make its data generically available to clients.
	# The server administrator determines what to make available, exporting the names and parameters of [[Directory (file systems)\|directories]], typically using the <code>/etc/exports</code> configuration file and the <code>exportfs</code> command.
	# The server [[network security\|security]]-administration ensures that it can recognize and approve validated clients.
	# The server network configuration ensures that appropriate clients can negotiate with it through any [[Firewall (networking)\|firewall]] system.
	# The client machine requests access to exported data, typically by issuing a <code>mount</code> command. (The client asks the server (rpcbind) which port the NFS server is using, the client connects to the NFS server (nfsd), nfsd passes the request to mountd)
	# If all goes well, users on the client machine can then view and interact with mounted [[filesystem]]s on the server within the parameters permitted.

	Automation of the NFS mounting process may take place — perhaps using <code>/etc/fstab</code> or [[Berkeley Automounter\|automounting]] facilities.

	== Protocol development ==		== Protocol development ==

164.215.242.60: /* See also */ Several of these items are extensively discussed in the prose. They don't belong here.

2024-10-21T21:20:26Z

See also: Several of these items are extensively discussed in the prose. They don't belong here.

← Previous revision		Revision as of 21:20, 21 October 2024
Line 144:		Line 144:

	== See also ==		== See also ==
	{{Div col\|colwidth=30em}}		{{Div col\|colwidth=30em}}* [[9P (protocol)]]

	* [[9P (protocol)]] – Plan 9 Filesystem Protocol
	* [[Alluxio]]		* [[Alluxio]]
	* [[~~Andrew File System~~]]		* [[BeeGFS]]
	* [[BeeGFS]], the parallel file system
	* [[CacheFS]] – a caching mechanism for Linux NFS clients		* [[CacheFS]] – a caching mechanism for Linux NFS clients
	* Hadoop Distributed File System ([[HDFS]])		* [[Hadoop Distributed File System]] (HDFS)
	* [[Kerberos (protocol)]]		* [[Kerberos (protocol)]]
	* [[Network Information Service]]		* [[Network Information Service]]
	* [[Remote File System]]		* [[Remote File System]]
	* [[Root squash]]		* [[Root squash]]
	* [[~~Samba~~ ~~(software)~~]]		* [[Secure Shell Filesystem]]
	* [[Secure Shell Filesystem]] – mount a remote directory using only a ssh login on the remote computer
	* [[Server Message Block]]
	* [[Shared resource]]		* [[Shared resource]]
	* [[TCP Wrapper]]		* [[TCP Wrapper]]{{Div col end}}

	{{Div col end}}

	==References==		==References==

164.215.242.60: Better summarized the available platform. Eliminated ad nauseam mentions of CIFS. Fine trivia of other subjects belong in their own articles.

2024-10-21T21:16:13Z

Better summarized the available platform. Eliminated ad nauseam mentions of CIFS. Fine trivia of other subjects belong in their own articles.

← Previous revision		Revision as of 21:16, 21 October 2024
Line 31:		Line 31:

	===NFSv4===		===NFSv4===
	Version 4 (RFC 3010, December 2000; revised in RFC 3530, April 2003 and again in RFC 7530, March 2015), influenced by [[Andrew File System]] (AFS) and [[Server Message Block]] (SMB~~, also termed CIFS~~), includes performance improvements, mandates strong security, and introduces a [[State (computer science)\|stateful]] protocol.<ref>{{cite web\|url=http://www.usenix.org/events/usenix05/tech/italks.html#nFSv4\|title=NFS Version 4\|date=2005-04-14\|publisher=[[USENIX]]}}</ref><ref name="sane2000">{{cite web \|url= http://www.sane.nl/events/sane2000/papers/pawlowski.pdf \|title=The NFS Version 4 Protocol \|year=2000 \|publisher=[[System Administration and Network Engineering\|SANE]] \|author1=Brian Pawlowski \|author2=Spencer Shepler \|author3=Carl Beame \|author4=Brent Callaghan \|author5=Michael Eisler \|author6=David Noveck \|author7=David Robinson \|author8=Robert Thurlow }}</ref> Version 4 became the first version developed with the [[Internet Engineering Task Force]] (IETF) after [[Sun Microsystems]] handed over the development of the NFS protocols.		Version 4 (RFC 3010, December 2000; revised in RFC 3530, April 2003 and again in RFC 7530, March 2015), influenced by [[Andrew File System]] (AFS) and [[Server Message Block]] (SMB), includes performance improvements, mandates strong security, and introduces a [[State (computer science)\|stateful]] protocol.<ref>{{cite web\|url=http://www.usenix.org/events/usenix05/tech/italks.html#nFSv4\|title=NFS Version 4\|date=2005-04-14\|publisher=[[USENIX]]}}</ref><ref name="sane2000">{{cite web \|url= http://www.sane.nl/events/sane2000/papers/pawlowski.pdf \|title=The NFS Version 4 Protocol \|year=2000 \|publisher=[[System Administration and Network Engineering\|SANE]] \|author1=Brian Pawlowski \|author2=Spencer Shepler \|author3=Carl Beame \|author4=Brent Callaghan \|author5=Michael Eisler \|author6=David Noveck \|author7=David Robinson \|author8=Robert Thurlow }}</ref> Version 4 became the first version developed with the [[Internet Engineering Task Force]] (IETF) after [[Sun Microsystems]] handed over the development of the NFS protocols.

	NFS version 4.1 (RFC 5661, January 2010; revised in RFC 8881, 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]].		NFS version 4.1 (RFC 5661, January 2010; revised in RFC 8881, 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]].
Line 74:		Line 74:
	== Platforms ==		== Platforms ==

			NFS is available on:
	NFS is often used with [[Unix]] operating systems (such as [[Solaris (operating system)\|Solaris]], [[AIX]], [[HP-UX]]), Apple's [[macOS]], and [[Unix-like]] operating systems (such as [[Linux]] and [[FreeBSD]]). It is also available to operating systems such as Acorn [[RISC OS]],<ref name="Sunfish/Moonfish by Alex Waugh">{{Cite web\|url=http://www.cp15.org/networking/\|title = Networking related programs\|website=cp15.org}}</ref> [[AmigaOS]], the [[classic Mac OS]], [[OpenVMS]],<ref name="NFSforVMS">{{cite web\|title=HP TCP/IP Services for OpenVMS Management\|url=http://h41379.www4.hpe.com/doc/83final/6526/6526pro_052.html\|website=h41379.www4.hpe.com\|publisher=HP\|access-date=24 September 2016\|archive-url=https://web.archive.org/web/20160924192510/http://h41379.www4.hpe.com/doc/83final/6526/6526pro_052.html\|archive-date=2016-09-24}}</ref> [[MS-DOS]],<ref name="PCNFS">{{cite web\|title=Other Software by SUN Microsystems\|url=http://www.computinghistory.org.uk/det/12549/PC-NFS%20version%205.0/\|website=www.computinghistory.org.uk\|publisher=The Centre for Computing History\|access-date=24 September 2016}}</ref> [[Microsoft Windows]],<ref name="SFU">{{cite web\|title=Introduction to Microsoft Windows Services for UNIX 3.5\|url=https://technet.microsoft.com/en-us/library/bb463212.aspx\|website=technet.microsoft.com\|date=5 December 2007 \|publisher=Microsoft\|access-date=24 September 2016}}</ref> [[OS/2]],<ref>{{cite web\|url=https://ecsoft2.org/network-file-system-nfs-plugin-netdrive\|access-date=2020-09-22\|website=ecsoft2.org\|title=NTFS plugin for NetDrive}}</ref> [[ArcaOS]],<ref>{{cite web\|url=https://www.arcanoae.com/shop/netdrive-for-os2/\|title=NetDrive for OS/2\|access-date=2020-09-22\|website=arcanoae.com}}</ref> [[Novell NetWare]],<ref name="NFSforNetWare">{{cite web\|title=NFS Gateway for NetWare 6.5\|url=https://www.novell.com/products/openenterpriseserver/features/nfs-gateway-for-netware65.html\|website=www.novell.com\|publisher=Novell\|access-date=24 September 2016}}</ref> and [[IBM i]].<ref name="OS/400-NFS">{{cite web\|title=OS/400 Network File System Support\|url=https://public.dhe.ibm.com/systems/power/docs/systemi/v5r4/en_US/sc415714.pdf\|publisher=IBM\|access-date=23 May 2024}}</ref> Alternative remote file access protocols include the [[Server Message Block]] (SMB, also termed CIFS), [[Apple Filing Protocol]] (AFP), [[NetWare Core Protocol]] (NCP), and OS/400 File Server file system (QFileSvr.400).

			* [[Unix-like]] operating systems ([[Solaris (operating system)\|Solaris]], [[AIX]], [[HP-UX]], [[FreeBSD]], and [[Linux distros]])
	SMB and [[NetWare Core Protocol]] (NCP) occur more often than NFS on systems running Microsoft Windows; AFP occurs more often than NFS in Apple [[Macintosh]] systems; and QFileSvr.400 occurs more often in IBM i systems. [[Haiku (operating system)\|Haiku]] in 2012 added NFSv4 support as part of a Google Summer of Code project.
			* [[macOS]], although the default networking protocol is [[Apple Filing Protocol]] (AFP)
			* Acorn [[RISC OS]]<ref name="Sunfish/Moonfish by Alex Waugh">{{Cite web\|url=http://www.cp15.org/networking/\|title = Networking related programs\|website=cp15.org}}</ref>
			* [[AmigaOS]]
			* [[OpenVMS]]<ref name="NFSforVMS">{{cite web\|title=HP TCP/IP Services for OpenVMS Management\|url=http://h41379.www4.hpe.com/doc/83final/6526/6526pro_052.html\|website=h41379.www4.hpe.com\|publisher=HP\|access-date=24 September 2016\|archive-url=https://web.archive.org/web/20160924192510/http://h41379.www4.hpe.com/doc/83final/6526/6526pro_052.html\|archive-date=2016-09-24}}</ref>
			* [[MS-DOS]]<ref name="PCNFS">{{cite web\|title=Other Software by SUN Microsystems\|url=http://www.computinghistory.org.uk/det/12549/PC-NFS%20version%205.0/\|website=www.computinghistory.org.uk\|publisher=The Centre for Computing History\|access-date=24 September 2016}}</ref>
			* [[Microsoft Windows]],<ref name="SFU">{{cite web\|title=Introduction to Microsoft Windows Services for UNIX 3.5\|url=https://technet.microsoft.com/en-us/library/bb463212.aspx\|website=technet.microsoft.com\|date=5 December 2007 \|publisher=Microsoft\|access-date=24 September 2016}}</ref> although the default networking protocol is [[Server Message Block]] (SMB)
			* [[OS/2]]<ref>{{cite web\|url=https://ecsoft2.org/network-file-system-nfs-plugin-netdrive\|access-date=2020-09-22\|website=ecsoft2.org\|title=NTFS plugin for NetDrive}}</ref>
			* [[ArcaOS]]<ref>{{cite web\|url=https://www.arcanoae.com/shop/netdrive-for-os2/\|title=NetDrive for OS/2\|access-date=2020-09-22\|website=arcanoae.com}}</ref>
			* [[Novell NetWare]],<ref name="NFSforNetWare">{{cite web\|title=NFS Gateway for NetWare 6.5\|url=https://www.novell.com/products/openenterpriseserver/features/nfs-gateway-for-netware65.html\|website=www.novell.com\|publisher=Novell\|access-date=24 September 2016}}</ref> although the defult networking protocol is [[NetWare Core Protocol]] (NCP)
			* [[IBM i]],<ref name="OS/400-NFS">{{cite web\|title=OS/400 Network File System Support\|url=https://public.dhe.ibm.com/systems/power/docs/systemi/v5r4/en_US/sc415714.pdf\|publisher=IBM\|access-date=23 May 2024}}</ref> although the default networking protocol is OS/400 File Server (QFileSvr.400)

			[[Haiku (operating system)\|Haiku]] in 2012 added NFSv4 support as part of a Google Summer of Code project.

	[[File:NfsPerformanceGraph.png\|thumb\|600px\|center\|NFS SPECsfs2008 performance comparison, as of 22 November 2013]]		[[File:NfsPerformanceGraph.png\|thumb\|600px\|center\|NFS SPECsfs2008 performance comparison, as of 22 November 2013]]
Line 92:		Line 104:
	# If all goes well, users on the client machine can then view and interact with mounted [[filesystem]]s on the server within the parameters permitted.		# If all goes well, users on the client machine can then view and interact with mounted [[filesystem]]s on the server within the parameters permitted.

	~~Note that automation~~ of the NFS mounting process may take place — perhaps using <code>/etc/fstab</code> ~~and/~~or [[Berkeley Automounter\|automounting]] facilities.		Automation of the NFS mounting process may take place — perhaps using <code>/etc/fstab</code> or [[Berkeley Automounter\|automounting]] facilities.

	== Protocol development ==		== Protocol development ==
Line 114:		Line 126:

	=== {{anchor\|PNFS}}2000s ===		=== {{anchor\|PNFS}}2000s ===
	By the 21st century, neither DFS nor AFS had achieved any major commercial success as compared to SMB~~-CIFS~~ or NFS. IBM, which had formerly acquired the primary commercial vendor of DFS and AFS, [[Transarc]], donated most of the AFS source code to the [[free software community]] in 2000. The [[OpenAFS]] project lives on. In early 2005, IBM announced end of sales for AFS and DFS.		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]], donated most of the AFS source code to the [[free software community]] in 2000. The [[OpenAFS]] project lives on. In early 2005, IBM announced end of sales for AFS and DFS.

	In January, 2010, [[Panasas]] proposed an NFSv4.1 based on their ''Parallel NFS'' (pNFS) technology claiming to improve data-access parallelism<ref>{{Cite web \|title= pNFS \|publisher= [[Panasas]] \|url= http://www.pnfs.com \|access-date= August 4, 2013 }}</ref> capability. The NFSv4.1 protocol defines a method of separating the [[metadata#File system metadata\|filesystem meta-data]] 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.		In January, 2010, [[Panasas]] proposed an NFSv4.1 based on their ''Parallel NFS'' (pNFS) technology claiming to improve data-access parallelism<ref>{{Cite web \|title= pNFS \|publisher= [[Panasas]] \|url= http://www.pnfs.com \|access-date= August 4, 2013 }}</ref> capability. The NFSv4.1 protocol defines a method of separating the [[metadata#File system metadata\|filesystem meta-data]] 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.

← Previous revision		Revision as of 06:02, 22 October 2024
Line 130:		Line 130:

	== See also ==		== See also ==
	{{Div col\|colwidth=30em}}* [[9P (protocol)]]		{{Div col\|colwidth=30em}}
			* [[9P (protocol)]]
	* [[Alluxio]]		* [[Alluxio]]
	* [[BeeGFS]]		* [[BeeGFS]]