Date: Sat, 14 Sep 2002 19:36:46 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Kris Kennaway <kris@obsecurity.org> Cc: "Andrew P. Lentvorski" <bsder@mail.allcaps.org>, Matthew Jacob <mjacob@feral.com>, current@freebsd.org Subject: Re: NFS lock failure (was Re: FreeBSD 5.0 as a desktop 'failure' report) Message-ID: <3D83F23E.9936A6D6@mindspring.com> References: <20020914202747.GB74535@xor.obsecurity.org> <20020914171333.M91535-100000@mail.allcaps.org> <20020915012837.GA943@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D83F23E.9936A6D6>