On 6 Apr 2008, at 09:58, Tz-Huan Huang wrote:
On Sun, Apr 6, 2008 at 3:45 PM, Doug Rabson <[EMAIL PROTECTED]> 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''.
One thing I did notice is that the client appears to be trying to
connect to the server on tcp port 751 and the server is rejecting that
connection. I'm not sure I trust the output of sockstat - could you
show me the output of rpcinfo and netstat -an.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
