From owner-freebsd-stable@FreeBSD.ORG Sun Apr 6 07:45:21 2008 Return-Path: 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 A9FA3106564A; Sun, 6 Apr 2008 07:45:21 +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 223428FC14; Sun, 6 Apr 2008 07:45: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 655D13F9F; Sun, 6 Apr 2008 08:45:20 +0100 (BST) Message-Id: From: Doug Rabson To: "Tz-Huan Huang" In-Reply-To: <6a7033710804052338l5af386f9xdd5c8d4729be2683@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 08:45:20 +0100 References: <6a7033710804020517y2b0a0336v7ab840ca5a5f5ff4@mail.gmail.com> <6a7033710804052218u3660441bk6d37458af03e7ed@mail.gmail.com> <6eb82e0804052305k4c44679dn92c86c58ac591cdc@mail.gmail.com> <6a7033710804052338l5af386f9xdd5c8d4729be2683@mail.gmail.com> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable@freebsd.org, dfr@freebsd.org, Rong-en Fan , Ken Chen 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Apr 2008 07:45:21 -0000 On 6 Apr 2008, at 07:38, Tz-Huan Huang wrote: > On Sun, Apr 6, 2008 at 2:05 PM, Rong-en Fan wrote: >> On Sun, Apr 6, 2008 at 1:18 PM, Tz-Huan Huang >> wrote: >>> Hi, >>> >>> Thanks for your suggestion, but we don't accept this workaround. >>> >>> After doing binary searching, I find that this commit break the >>> working lockd: >>> >>> http://lists.freebsd.org/pipermail/cvs-src/2008-March/089037.html >>> >>> I have rolled back the lockd.c to 1.20 in our nfs server and it >>> works >>> fine as before. >> >> Add dfr@ to CC list. >> >> I'm curious about this change, could you check what socket bind by >> rpc.lockd and rpc.statd before and after lockd. rev 1.21+1.22 >> changes? > > Ok, following is the output of sockstat -4l : > > Before the changes: > daemon rpc.lockd 83002 3 udp4 *:677 *:* > daemon rpc.lockd 83002 4 tcp4 *:946 *:* > daemon rpc.lockd 83002 7 udp4 *:642 *:* > root rpc.lockd 83001 3 udp4 *:677 *:* > root rpc.lockd 83001 4 tcp4 *:946 *:* > root rpc.lockd 83001 7 udp4 *:642 *:* > root rpc.statd 973 3 udp4 *:964 *:* > root rpc.statd 973 4 tcp4 *:602 *:* > > After the changes: > (with -h 140.112.29.133) > daemon rpc.lockd 82817 4 udp4 127.0.0.1:696 *:* > daemon rpc.lockd 82817 5 udp4 140.112.29.133:696 *:* > daemon rpc.lockd 82817 6 tcp4 127.0.0.1:696 *:* > daemon rpc.lockd 82817 7 tcp4 140.112.29.133:696 *:* > daemon rpc.lockd 82817 9 udp4 *:974 *:* > root rpc.lockd 82816 4 udp4 127.0.0.1:696 *:* > root rpc.lockd 82816 5 udp4 140.112.29.133:696 *:* > root rpc.lockd 82816 6 tcp4 127.0.0.1:696 *:* > root rpc.lockd 82816 7 tcp4 140.112.29.133:696 *:* > root rpc.lockd 82816 9 udp4 *:974 *:* > root rpc.statd 973 3 udp4 *:964 *:* > root rpc.statd 973 4 tcp4 *:602 *:* > > (without -h 140.112.29.133) > daemon rpc.lockd 82541 4 udp4 *:915 *:* > daemon rpc.lockd 82541 5 tcp4 *:915 *:* > daemon rpc.lockd 82541 7 udp4 *:713 *:* > root rpc.lockd 82540 4 udp4 *:915 *:* > root rpc.lockd 82540 5 tcp4 *:915 *:* > root rpc.lockd 82540 7 udp4 *:713 *:* > root rpc.statd 973 3 udp4 *:964 *:* > root rpc.statd 973 4 tcp4 *:602 *:* > > More information would be provided if necessary. It would be useful to get a packet trace from tcpdump (e.g. tcpdump -w ) that shows what happens on the wire when the linux client fails to lock a file on the freebsd server.