1
0
mirror of https://git.FreeBSD.org/src.git synced 2025-01-30 16:51:41 +00:00

Document the fact that an NFSv4 mount against a volume on the same host

can result in a hung NFS server and is not recommended.
This is a content change.

MFC after:	2 weeks
This commit is contained in:
Rick Macklem 2013-05-01 22:50:45 +00:00
parent ed5987bd08
commit 2eec079956
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=250162

View File

@ -24,7 +24,7 @@
.\"
.\" $FreeBSD$
.\"
.Dd December 23, 2012
.Dd May 1, 2013
.Dt NFSV4 4
.Os
.Sh NAME
@ -287,6 +287,13 @@ and
daemons at boot time via the ``nfsuserd_flags'' and ``nfscbd_flags''
.Xr rc.conf 5
variables.
.Pp
NFSv4 mount(s) against exported volume(s) on the same host are not recommended,
since this can result in a hung NFS server.
It occurs when an nfsd thread tries to do an NFSv4 VOP_RECLAIM()/Close RPC
as part of acquiring a new vnode.
If all other nfsd threads are blocked waiting for lock(s) held by this nfsd
thread, then there isn't an nfsd thread to service the Close RPC.
.Sh FILES
.Bl -tag -width /var/db/nfs-stablerestart.bak -compact
.It Pa /var/db/nfs-stablerestart