Re: is NetBSD-4.x NFS Server locking support broken?

[christos%astron.com@localhost (Christos Zoulas)]

In article <m1KgnPE-000kmP0%most.weird.com@localhost>,
Greg A. Woods <tech-net%NetBSD.org@localhost> wrote:
>-=-=-=-=-=-
>
>Is NetBSD-4.x NFS Server locking support broken?
>
>(I sure wish NetBSD NFS Client locking worked!)

somebody wrote the code and posted a patch. We should integrate it.

>
>Since upgrading my Apple laptop to OS X 10.5 I've been having problems
>with NFS mounts to my NetBSD-4 server.
>
>The first few times it happened I finally came to suspect locking, after
>eventually spotting messages like the following in my system logs:
>
>Sep 19 17:10:17 once rpc.lockd: clntudp_create: RPC: Port mapper failure
>- RPC: Timed out
>Sep 19 17:10:17 once rpc.lockd: Unable to return result to 204.92.254.251
>Sep 19 17:10:17 once rpc.lockd: lock from macweird.local.8243: already
>locked, failed
>
>I've learned to work around the problem with the "nolock" option on OS X:
>
>       mount -r -o -P,i,tcp,nolock once:/rest /once/rest
>
>I think I have all the right services running on the NetBSD server:
>
>       rpcbind=YES
>       nfs_server=YES nfsd_flags="-tu -n 4"
>       mountd=YES
>       lockd=YES
>       statd=YES
>
>17:11 [272] $ showmount -a
>All mount points on localhost:
>ethereal.weird.com:/rest
>17:12 [273] $ showmount -e     
>Exports list on localhost:
>/var                               204.92.254.0 
>/rest                              204.92.254.0 
>17:12 [274] $ rpcinfo -p    
>   program vers proto   port  service
>    100000    4   tcp    111  portmapper
>    100000    3   tcp    111  portmapper
>    100000    2   tcp    111  portmapper
>    100000    4   udp    111  portmapper
>    100000    3   udp    111  portmapper
>    100000    2   udp    111  portmapper
>    100000    4     0    111  portmapper
>    100000    3     0    111  portmapper
>    100000    2     0    111  portmapper
>    100005    1   udp   1021  mountd
>    100005    3   udp   1021  mountd
>    100005    1   tcp   1022  mountd
>    100005    3   tcp   1022  mountd
>    100003    2   udp   2049  nfs
>    100003    3   udp   2049  nfs
>    100003    2   tcp   2049  nfs
>    100003    3   tcp   2049  nfs
>    100001    1   udp  65495  rstatd
>    100001    2   udp  65495  rstatd
>    100001    3   udp  65495  rstatd
>    100002    2   udp  65494  rusersd
>    100002    3   udp  65494  rusersd
>    100008    1   udp  65493  walld
>    100011    1   udp  65492  rquotad
>    100011    2   udp  65492  rquotad
>    100024    1   udp    993  status
>    100024    1   tcp   1010  status
>    100021    0   udp    992  nlockmgr
>    100021    1   udp    992  nlockmgr
>    100021    3   udp    992  nlockmgr
>    100021    4   udp    992  nlockmgr
>    100021    0   tcp   1009  nlockmgr
>    100021    1   tcp   1009  nlockmgr
>    100021    3   tcp   1009  nlockmgr
>    100021    4   tcp   1009  nlockmgr
>
>
>The only thing potentially odd here is that my Macbook is connected
>through a NAT (running on my SMC wireless AP).
>
>Can anyone else confirm this?
>
>What more debugging should I try?  (next time I reboot the mac I'll try
>to remember to try a wired connection to avoid the NAT)
>
>I guess I could try "rpc.lockd -d" too....

Yes... Something seems busted with the locking protocol. I suspect OSX/X.

christos