Date: Sat, 14 Sep 2002 19:50:39 -0700 From: Kris Kennaway <kris@obsecurity.org> 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: <20020915025039.GA2139@xor.obsecurity.org> In-Reply-To: <20020915012837.GA943@xor.obsecurity.org> 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
[-- Attachment #1 --] On Sat, Sep 14, 2002 at 06:28:37PM -0700, 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. I see pretty much the same problem when running the test suite against localhost; the locking test blocks in fcntl() when it shouldn't be. 89182 tlock 0.000507 RET write 44/0x2c 89182 tlock 0.000071 CALL fcntl(0x7,0x7,0xbfbff680) 89182 tlock 0.000025 NAMI "/var/run/lock" 89183 tlock 1.568295 RET read RESTART 89182 tlock 0.000152 RET fcntl RESTART #define F_GETLK 7 /* get record locking information */ It looks like something is wrong with file locking. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9g/V+Wry0BWjoQKURAqtKAJ0ZMykg2xVa1T6YnjsTobmPbKuxAwCdFuvY vwXbF+dD10JZbn+fuaH6YVU= =jQwa -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020915025039.GA2139>