NFS Hangs ... NFS4ERR_DELAY

[J. Bruce Fields]

On Mon, Dec 10, 2007 at 11:44:30AM -0500, Norman Elton wrote:
> Hello,
> 
> I wrote last week regarding NFS hangs as we're migrating towards NFS4  
> + Kerberos. I believe I've got all the kerberos issues straightened  
> out, but we're experiencing hung connections, both when mounting and  
> when doing an "ls" of individual shares.
> 
> Here's the dialogue I've observed with tcpdump when mounting a share:
> 
>  >>> V4 Null Call
> <<< V4 Null Reply
>  >>> V4 Null Call
> <<< V4 Null Reply
>  >>> V4 Null Call, now with GSS Token
> <<< V4 Null Reply, again, with GSS information
>  >>> V4 Compound Request (PUTROOTFH, GETFH, GETATTR)
> <<< V4 Compound Reply (PUTROOTFH=ok, GETFH=ok, GETATTR=nfs4err_delay)
> 
> This last transaction goes back and forth a few times, with the  
> GETATTR operation consistently returning NFS4ERR_DELAY. Eventually I  
> have to kill the mount request.
> 
> A little googling indicates that this could be a problem with idmapd.  
> I've configured our DNS domain in idmapd.conf, no luck. I've run  
> idmapd in debug mode ("-f -vvv") and do not get any output. I'm not  
> sure if idmapd is functioning properly or not.
> 
> Any ideas?

Could you check which files idmapd has open?  (ls -l /proc/`pidof
idmapd`/fd/, or lsof rpc.idmapd).

Also, is nfsd built as a module, and is there a chance you're starting
rpc.idmapd before loading that module?

--b.