From owner-freebsd-current Sat Sep 14 22: 4:29 2002 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 9FAAB37B400 for ; Sat, 14 Sep 2002 22:04:28 -0700 (PDT) Received: from mail.allcaps.org (h-66-166-142-198.SNDACAGL.covad.net [66.166.142.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82ACA43E4A for ; Sat, 14 Sep 2002 22:04:27 -0700 (PDT) (envelope-from bsder@mail.allcaps.org) Received: by mail.allcaps.org (Postfix, from userid 501) id 8C7D3154FD; Sat, 14 Sep 2002 22:04:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.allcaps.org (Postfix) with ESMTP id 80C1E154FC; Sat, 14 Sep 2002 22:04:22 -0700 (PDT) Date: Sat, 14 Sep 2002 22:04:22 -0700 (PDT) From: "Andrew P. Lentvorski" To: Kris Kennaway Cc: Matthew Jacob , Subject: Re: NFS lock failure (was Re: FreeBSD 5.0 as a desktop 'failure' report) In-Reply-To: <20020915030002.GA2484@xor.obsecurity.org> Message-ID: <20020914215026.A91907-100000@mail.allcaps.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Sat, 14 Sep 2002, Kris Kennaway wrote: > ... When the machine > rebooted (with a newer kernel, hmm) it is now completing the locking > tests (note the warnings, though). My locking problems with the linux > server continue though. Cool! I'm glad that FreeBSD -current passes the new Connectathon 2002 locking suites (especially when run by somebody other than me :-) ). Your linux problems are not surprising. The linux NFS server did not support partial file locking last time I checked. It also did not support certain combinations of rpc binding(portmapper/rpcbind), NFS version, and NFS lock manager verion. However, NFS on linux is Somebody Else's Problem(tm). The lack of partial file locking was the reason that I rewrote a whole lot of rpc.lockd on -current. Even after this rewrite, rpc.lockd still has some quirks on -current which will require some significant kernel digging to rectify. However, some of this should get easier given the significant efforts which have gone into the filesystem code in -current. -a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message