d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

mount_nfs.8: Note a case where the "nconnect" option does not work

Browse Source 
The "nconnect" NFS mount option will not work
correctly for servers where the TCP connections
might connect to different NFS clusters that do not
share NFSv4.1/4.2 state information, such as file locks.

This patch adds a sentence to the "nconnect" section
of mount_nfs.8 noting this case.

This is a content change.

Reviewed by:	karels, pauamma_gundo.com (manpages)
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D40547
This commit is contained in:
Rick Macklem 2023-06-18 13:02:20 -07:00
parent ab3e6234ab
commit 7e53f16baa
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
sbin/mount_nfs/mount_nfs.8
View File

@ -28,7 +28,7 @@
.\" @(#)mount_nfs.8 8.3 (Berkeley) 3/29/95
.\" $FreeBSD$
.\"
.Dd April 3, 2023
.Dd June 14, 2023
.Dt MOUNT_NFS 8
.Os
.Sh NAME
@ -231,6 +231,9 @@ This option will result in more IP port#s being used.
This option requires the
.Cm nfsv4
option.
Note that for NFS servers such as AmazonEFS, where each new TCP
connection can connect to a different cluster that maintains lock
state separately, this option cannot be used.
.It Cm nfsv2
Use the NFS Version 2 protocol (the default is to try version 3 first
then version 2).