Date: Tue, 2 Aug 2005 11:27:35 -0400 (EDT) From: rick@snowhite.cis.uoguelph.ca To: kris@obsecurity.org Cc: fs@freebsd.org, openbsd-nfsv4@sfobug.org Subject: Re: Re: FreeBSD6.0-BETA1 panics Message-ID: <200508021527.LAA45116@snowhite.cis.uoguelph.ca>
next in thread | raw e-mail | index | archive | help
> I suspect the server is returning bogus data, perhaps because of the > locking problems. My server doesn't support the lockd/statd protocol, so v3 mounts won't have any advisory locking support. Is that likely to be the cause of this? (I don't know anything about the inner workings of cvs.) > OK, I triggered another deadlock while running a simultaneous cvs > checkout on the server (via ufs) and over nfs3 from a remote machine. Ok, thanks for the info. I'll try and figure this one out. (Given your original panic, I assume you're running a kernel with DEBUG_LOCKS and DEBUG_VFS_LOCKS options? That would have caught the obvious "forgot to unlock the vnode" type problems, which would suggest a race between the local ufs syscall and newnfsd for vnode locking. Could be a fun one to find:-) Thanks for the debug info, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200508021527.LAA45116>