NFS lockd/statd lock up network connection

[Doug Rabson]

On 5 Apr 2009, at 07:38, Tom McLaughlin wrote:

> Hey, I have a recent -CURRENT box which has a mount exported from an
> OpenBSD NFS server.  Recently I enabled lockd and statd on the machine
> but this has started to cause the network connection on the machine  
> to lockup.  I find the following in dmesg:
>
> nfs server exports:/mnt/raid0/net/home: lockd not responding
> nfs server exports:/mnt/raid0/net/home: lockd not responding
> nfs server exports:/mnt/raid0/net/home: lockd not responding
> nfs server exports:/mnt/raid0/net/home: lockd not responding
> nfs server exports:/mnt/raid0/net/home: lockd not responding
> nfs server exports:/mnt/raid0/net/home: lockd not responding
> nfs server exports:/mnt/raid0/net/home: lockd not responding
> nfs server exports:/mnt/raid0/net/home: lockd not responding
> NLM: failed to contact remote rpcbind, stat = 5, port = 28416
>
> Additionally I see this when trying to restart netif:
>
> em0: Could not setup receive structures
>
> I've tried building with NFS_LEGACYRPC but that has not changed  
> anything.  Additionally I've tested this on 7-STABLE and while lockd  
> still does not work (so, looks like I'll still have to work around  
> my need for NFS locking) the network connection at least does not  
> lock up.  Is what I'm seeing evidence of some further problem?

It looks as if lockd is not running on the server. The NFS locking  
protocol needs it enabled at both ends. Also, NFS_LEGACYRPC won't  
affect this - the record locking code always uses the new RPC code.