svn commit: r250654 - stable/9/usr.sbin/nfsd

[Rick Macklem]

Author: rmacklem
Date: Wed May 15 01:44:01 2013
New Revision: 250654
URL: http://svnweb.freebsd.org/changeset/base/250654

Log:
  MFC: r250162
  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.

Modified:
  stable/9/usr.sbin/nfsd/nfsv4.4
Directory Properties:
  stable/9/usr.sbin/nfsd/   (props changed)

Modified: stable/9/usr.sbin/nfsd/nfsv4.4
==============================================================================
--- stable/9/usr.sbin/nfsd/nfsv4.4	Wed May 15 01:40:16 2013	(r250653)
+++ stable/9/usr.sbin/nfsd/nfsv4.4	Wed May 15 01:44:01 2013	(r250654)
@@ -24,7 +24,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd December 23, 2012
+.Dd May 1, 2013
 .Dt NFSV4 4
 .Os
 .Sh NAME
@@ -289,6 +289,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