From owner-freebsd-current Sat Sep 14 19:43:25 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 791C437B400 for ; Sat, 14 Sep 2002 19:43:24 -0700 (PDT) Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10D9143E6A for ; Sat, 14 Sep 2002 19:43:24 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0261.cvx40-bradley.dialup.earthlink.net ([216.244.43.6] helo=mindspring.com) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17qPMi-0005jX-00; Sat, 14 Sep 2002 19:42:29 -0700 Message-ID: <3D83F23E.9936A6D6@mindspring.com> Date: Sat, 14 Sep 2002 19:36:46 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: "Andrew P. Lentvorski" , Matthew Jacob , current@freebsd.org Subject: Re: NFS lock failure (was Re: FreeBSD 5.0 as a desktop 'failure' report) References: <20020914202747.GB74535@xor.obsecurity.org> <20020914171333.M91535-100000@mail.allcaps.org> <20020915012837.GA943@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Kris Kennaway wrote: > On Sat, Sep 14, 2002 at 05:51:32PM -0700, Andrew P. Lentvorski wrote: > > Folks, > > > > Could someone *please* take a look at the NFS lock packets *on the wire*? > > Without this, it becomes significantly harder to debug the failure. > > Well, there's also the apparent problem of a non-blocking flock() > operation blocking on the named pipe..but thanks for your suggestions, > I'll go and try them out now. FIFO's don't support flock(), even in the HEAD, because FreeBSD file locks are hung off the inode by the underlying FS in the VOP_ADVLOCK routine, instead of being set in the vnode at a higher layer, after the VOP_ADVLOCK call returns "proceed" instead of "cancel" (for NFS, this would require real work; all other FS's (non-stacking ones) would merely return "proceed", since there were no operations to proxy; the stacking ones would call down, and return that as their result). You should break into the kernel debgger and see where it's hanging, since it's not hanging where you think it is. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message