Date: Wed, 21 Sep 2022 01:17:41 GMT From: Rick Macklem <rmacklem@FreeBSD.org> To: src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-branches@FreeBSD.org Subject: git: a72dee6742c4 - stable/12 - mount_nfs.8: Update for NFSv4 use of "nolockd" Message-ID: <202209210117.28L1HfJi044647@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch stable/12 has been updated by rmacklem: URL: https://cgit.FreeBSD.org/src/commit/?id=a72dee6742c4e7b9beafcb15b15243b92381eb2d commit a72dee6742c4e7b9beafcb15b15243b92381eb2d Author: Rick Macklem <rmacklem@FreeBSD.org> AuthorDate: 2022-09-07 21:07:20 +0000 Commit: Rick Macklem <rmacklem@FreeBSD.org> CommitDate: 2022-09-21 01:13:38 +0000 mount_nfs.8: Update for NFSv4 use of "nolockd" Commit 33721eb991d8 enabled use of "nolockd" for NFSv4 mounts. This was done primarily to allow its use with the "intr" mount option. This patch updates the man page for this. This is a content change. (cherry picked from commit 9b436906fa10b8bec4f7c231b389ed9ef5b2acad) --- sbin/mount_nfs/mount_nfs.8 | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/sbin/mount_nfs/mount_nfs.8 b/sbin/mount_nfs/mount_nfs.8 index 1b83687d950f..a99ace2d1c82 100644 --- a/sbin/mount_nfs/mount_nfs.8 +++ b/sbin/mount_nfs/mount_nfs.8 @@ -28,7 +28,7 @@ .\" @(#)mount_nfs.8 8.3 (Berkeley) 3/29/95 .\" $FreeBSD$ .\" -.Dd August 31, 2022 +.Dd September 5, 2022 .Dt MOUNT_NFS 8 .Os .Sh NAME @@ -186,6 +186,10 @@ Same as not specifying Make the mount interruptible, which implies that file system calls that are delayed due to an unresponsive server will fail with EINTR when a termination signal is posted for the process. +To avoid leaving file locks in an indeterminate state on the NFS +server, it is recommended that the +.Cm nolockd +option be used with this option. .It Cm maxgroups Ns = Ns Aq Ar value Set the maximum size of the group list for the credentials to the specified value. @@ -295,19 +299,23 @@ Do .Em not forward .Xr fcntl 2 -locks over the wire. +locks over the wire via the NLM protocol for NFSv3 mounts +or via the NFSv4 protocol for NFSv4 mounts. All locks will be local and not seen by the server -and likewise not seen by other NFS clients. +and likewise not seen by other NFS clients for NFSv3 or NFSv4 mounts. This removes the need to run the .Xr rpcbind 8 service and the .Xr rpc.statd 8 and .Xr rpc.lockd 8 -servers on the client. +servers on the client for NFSv3 mounts. Note that this option will only be honored when performing the initial mount, it will be silently ignored if used while updating the mount options. +Also, note that NFSv4 mounts do not use these daemons. +The NFSv4 protocol handles locks, +unless this option is specified. .It Cm noncontigwr This mount option allows the NFS client to combine non-contiguous byte ranges being written @@ -575,7 +583,7 @@ A version of the utility appeared in .Bx 4.4 . .Sh BUGS -Since nfsv4 performs open/lock operations that have their ordering strictly +Since NFSv4 performs open/lock operations that have their ordering strictly enforced by the server, the options .Cm intr and @@ -584,5 +592,8 @@ cannot be safely used. For NFSv4 minor version 1 mounts, these options may also result in hung mount points, due to corruption of session slots. +For NFSv4 mounts, .Cm hard -nfsv4 mounts are strongly recommended. +mounts without the +.Cm intr +mount option is strongly recommended.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202209210117.28L1HfJi044647>