NFS Hangs ... NFS4ERR_DELAY (Solved)

[Norman Elton]

Bruce,

A little poking into idmapd has resolved the problem. I configured  
idmapd to run with "-v" on the server, and found this error in the  
system log:

nfsdcb: id '-2' too big!

On my 64-bit machine, nfsnobody has the ID of 4294967294. This appears  
to cause idmapd to choke and stop responding. I've changed it back to  
the 32-bit version (65534) and things seem to be working as expected.

I'll probably drop the list another note if I find any more problems.  
Thanks again for your help!!!

Norman Elton


On Dec 10, 2007, at 3:00 PM, J. Bruce Fields wrote:

> On Mon, Dec 10, 2007 at 02:48:11PM -0500, Norman Elton wrote:
>> I've posted the results from an strace on the client's idmapd:
>>
>> http://pastebin.com/f760d62b5
>
> Sorry, I should have just asked for the server; the client's not the
> problem here.
>
>> Running strace on the server's idmapd doesn't seem to produce
>> anything. It looks like idmapd is only consulted on the client's  
>> side.
>
> OK, that's wrong.
>
> Is there anything in
>
> 	cat /proc/net/rpc/nfs4.idtoname/content
>
> ?
>
>> I see some errors about /var/lib/nfs/rpc_pipefs/nfs/clnt4d/idmap not
>> existing. In my case, /var/lib/nfs/rpc_pipefs/nfs is empty.
>
> Let's ignore any client-side errors, the problem is those  
> NFS4ERR_DELAY
> returns from the server.
>
> --b.