Date: Mon, 1 Aug 2005 14:57:19 -0400 From: Kris Kennaway <kris@obsecurity.org> To: rick@snowhite.cis.uoguelph.ca Cc: openbsd-nfsv4@sfobug.org, fs@freebsd.org, kris@obsecurity.org Subject: Re: FreeBSD6.0-BETA1 panics Message-ID: <20050801185719.GA26377@xor.obsecurity.org> In-Reply-To: <200508010127.VAA29962@snowhite.cis.uoguelph.ca> References: <200508010127.VAA29962@snowhite.cis.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 31, 2005 at 09:27:43PM -0400, rick@snowhite.cis.uoguelph.ca wro= te: > I've just put a little patch up > ftp://ftp.cis.uoguelph.ca/pub/nfsv4/patch2-freebsd6.0-bet1.diffc > (which is also appended to this message) that seems to fix the panics > that I reproduced when testing with: > option DEBUG_VFS_LOCKS > option DEBUG_LOCKS >=20 > I will be doing further testing on FreeBSD6.0-BETA1 and will cut new > tarballs, but you can try the patch in the meantime, since I think it > fixes the panic you saw. It didn't panic yet, but when doing a multiple simultaneous cvs update with NFS3 mounted repo the clients eventually got stuck in the nfsreq state. FreeBSD had a similar problem for a while, after a change made last December, but it was fixed early this year. Is your server based on an old version of the freebsd server code that is missing this (and possibly other) fixes, or is this a new bug introduced in your version? Kris --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC7nCPWry0BWjoQKURAtlsAKCPQu7S5QP+39BRmSfQRwrlVce3jQCeJsPD Q1w2Gx7pSMJBTEAtvNtamco= =8XMj -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050801185719.GA26377>