lock problem: nfs server on FreeBSD 7-stable, client on linux

[Tz-Huan Huang]

On Sun, Apr 6, 2008 at 3:45 PM, Doug Rabson <dfr at rabson.org> wrote:
>
>  It would be useful to get a packet trace from tcpdump (e.g. tcpdump -w
> <file>) that shows what happens on the wire when the linux client fails to
> lock a file on the freebsd server.

Since the nfs server is in production now, I have setup another machine to
get the packet trace.

Here is the output of tcpdump (I use tcpdump -w host cml8):

   http://w.csie.org/~tzhuan/tmp/tcpdump.raw

cml7 is the nfs server (today's 7-stable, i386) and cml8 is debian
linux (amd64).
I use this program (http://w.csie.org/~tzhuan/tmp/lock.c) to test the
file locking
when capturing the packets.  It ran about 1m30s and showed ``lock fail''.

sockstat -4l on cml7:

root     sshd       695   3  tcp4   *:22                  *:*
daemon   rpc.lockd  577   4  udp4   *:751                 *:*
daemon   rpc.lockd  577   5  tcp4   *:751                 *:*
daemon   rpc.lockd  577   7  udp4   *:716                 *:*
root     rpc.lockd  565   4  udp4   *:751                 *:*
root     rpc.lockd  565   5  tcp4   *:751                 *:*
root     rpc.lockd  565   7  udp4   *:716                 *:*
root     rpc.statd  559   3  udp4   *:739                 *:*
root     rpc.statd  559   4  tcp4   *:686                 *:*
root     rpc.statd  558   3  udp4   *:739                 *:*
root     rpc.statd  558   4  tcp4   *:686                 *:*
root     nfsd       551   3  tcp4   *:2049                *:*
root     mountd     542   5  udp4   *:608                 *:*
root     mountd     542   7  tcp4   *:608                 *:*
root     rpcbind    497   6  udp4   *:111                 *:*
root     rpcbind    497   7  udp4   *:725                 *:*
root     rpcbind    497   8  tcp4   *:111                 *:*

Thanks,
Tz-Huan