From owner-freebsd-current Thu Mar 20 22:46: 7 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83AD437B401 for ; Thu, 20 Mar 2003 22:46:05 -0800 (PST) Received: from Math.Berkeley.EDU (gold.Math.Berkeley.EDU [169.229.58.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id C676E43FAF for ; Thu, 20 Mar 2003 22:46:02 -0800 (PST) (envelope-from steve@Math.Berkeley.EDU) Received: from bootjack.math.berkeley.edu (root@bootjack.Math.Berkeley.EDU [169.229.58.46]) by Math.Berkeley.EDU (8.12.8/8.12.8) with ESMTP id h2L6jweB001067; Thu, 20 Mar 2003 22:45:58 -0800 (PST) Received: from bootjack.math.berkeley.edu (steve@localhost [127.0.0.1]) by bootjack.math.berkeley.edu (8.12.6/8.12.6) with ESMTP id h2L6jrUu040796; Thu, 20 Mar 2003 22:45:53 -0800 (PST) (envelope-from steve@bootjack.math.berkeley.edu) Received: (from steve@localhost) by bootjack.math.berkeley.edu (8.12.6/8.12.6/Submit) id h2L6jmKt040795; Thu, 20 Mar 2003 22:45:48 -0800 (PST) (envelope-from steve) Date: Thu, 20 Mar 2003 22:45:48 -0800 From: Steve Sizemore To: "Andrew P. Lentvorski, Jr." Cc: Dan Nelson , current@freebsd.org Subject: Re: NFS file unlocking problem Message-ID: <20030321064547.GB40697@math.berkeley.edu> Reply-To: Steve Sizemore References: <20030317060216.GB45288@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Mar 19, 2003 at 05:15:02PM -0800, Andrew P. Lentvorski, Jr. wrote: > Steve, > > I actually managed to pull down the dump. It doesn't have any lock > requests in it. It looks like it is hanging in the rpcinfo call. > > If you really want to debug this, it's going to take a chunk of work. > > 1) set up two brand new machines > FreeBSD-current for the server > Solaris whatever for the client > Well, I think I found the problem. I had just installed the new FreeBSD machine, not looking forward to finding another Sun to install, when I had the idea to try different nfs protocols. By default, it looks like the NFS mount is version 3 tcp. I specified udp, and both of the test programs (mine and Terry's) work consistently. I've reenabled locking on the Xinet software, and we'll see (tomorrow) whether or not that also works. If I'm right, that means that there is a problem with nfs over tcp with a Solaris client and FreeBSD-5 server. All other combinations of client/server pairs worked with the default (which I assume is version 3 tcp). BTW, Terry's testlock program, when run with the problem configuration, would always return the "There is nothing that would block your lock" message, but it could take anywhere from < 1 second to >45 minutes. I'm not so confident that my perl program would always succeed, because I was never willing to wait longer than overnight before concluding that it was hung. I'll report back on the status of xinet tomorrow, but thanks to all of you for your help and suggestions. If there's any more information I can provide, or testing that I can do, to help fix the NFS/tcp/Solaris problem, let me know. Thanks. Steve -- Steve Sizemore , (510) 642-8570 Unix System Manager Dept. of Mathematics and College of Letters and Science University of California, Berkeley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message