From owner-freebsd-stable@FreeBSD.ORG  Sun Apr  6 09:53:22 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 08E721065671;
	Sun,  6 Apr 2008 09:53:22 +0000 (UTC) (envelope-from dfr@rabson.org)
Received: from itchy.rabson.org (mail.rabson.org [IPv6:2002:50b1:e8f2:1::143])
	by mx1.freebsd.org (Postfix) with ESMTP id A85A88FC18;
	Sun,  6 Apr 2008 09:53:21 +0000 (UTC) (envelope-from dfr@rabson.org)
Received: from [IPv6:2002:50b1:e8f2:1:21b:63ff:feb8:5abc] (unknown
	[IPv6:2002:50b1:e8f2:1:21b:63ff:feb8:5abc])
	by itchy.rabson.org (Postfix) with ESMTP id 9BFAC3F9F;
	Sun,  6 Apr 2008 10:53:20 +0100 (BST)
Message-Id: <8BB84DC5-36D9-4487-BC04-AA8C8285B947@rabson.org>
From: Doug Rabson <dfr@rabson.org>
To: Tz-Huan Huang <tzhuan@csie.org>
In-Reply-To: <6a7033710804060158j38c1314u371130b05225c247@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sun, 6 Apr 2008 10:53:20 +0100
References: <6a7033710804020517y2b0a0336v7ab840ca5a5f5ff4@mail.gmail.com>
	<d018a9bd0804021002n3a6234e7y66c2b50a1594afe9@mail.gmail.com>
	<6a7033710804052218u3660441bk6d37458af03e7ed@mail.gmail.com>
	<6eb82e0804052305k4c44679dn92c86c58ac591cdc@mail.gmail.com>
	<6a7033710804052338l5af386f9xdd5c8d4729be2683@mail.gmail.com>
	<AEECB0A1-E0B5-4443-9063-96C69F2CFA5D@rabson.org>
	<6a7033710804060158j38c1314u371130b05225c247@mail.gmail.com>
X-Mailer: Apple Mail (2.919.2)
Cc: freebsd-stable@freebsd.org, dfr@freebsd.org, Rong-en Fan <grafan@gmail.com>,
	Ken Chen <ken73.chen@gmail.com>
Subject: Re: lock problem: nfs server on FreeBSD 7-stable, client on linux
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2008 09:53:22 -0000


On 6 Apr 2008, at 09:58, Tz-Huan Huang wrote:

> On Sun, Apr 6, 2008 at 3:45 PM, Doug Rabson <dfr@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''.

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.