From owner-freebsd-fs Sun Mar 3 14: 7:38 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 2FE5337B402 for ; Sun, 3 Mar 2002 14:07:34 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9221566C39; Sun, 3 Mar 2002 14:07:33 -0800 (PST) Date: Sun, 3 Mar 2002 14:07:32 -0800 From: Kris Kennaway To: Kris Kennaway Cc: Kirk McKusick , Ian Dowse , Matthew Dillon , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020303140732.A45711@xor.obsecurity.org> References: <200203022233.aa08277@salmon.maths.tcd.ie> <200203031917.g23JH9g02868@beastie.mckusick.com> <20020303134757.C45350@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020303134757.C45350@xor.obsecurity.org>; from kris@obsecurity.org on Sun, Mar 03, 2002 at 01:47:57PM -0800 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 03, 2002 at 01:47:57PM -0800, Kris Kennaway wrote: > On Sun, Mar 03, 2002 at 11:17:04AM -0800, Kirk McKusick wrote: >=20 > > Of the recent changes that I have been involved with, the one > > above is the one that I would be most suspicious of. The problems > > seem to be showing up independent of soft updates, and the > > VOP_INACTIVE one is the only change of mine that would have > > that property. >=20 > There seem to be about half a dozen panics I'm seeing here. The > evidence so far does not contradict the hypothesis that the > VOP_INACTIVE change is responsible for some of them, but for example > one of the cluster machines double faulted again last night, and it > was running a kernel which does not have that change. One of the > alpha machines experienced a different UFS panic the other day too. Okay, bad news..gohan10 just panicked with the 'ufs_dirbad: bad dir' panic, and I'm pretty sure it was running 1.249.2.23 of vfs_subr.c, which is the version before both matt's vnlru change and the VOP_INACTIVE one (the version included in 4.5-RELEASE, in fact). The double fault last night was with 1.249.2.24 but when it rebooted it picked up the new kernel in the nfsroot image, which has 1.249.2.23, and then it panicked about 10 minutes later. Kris --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8gp6kWry0BWjoQKURAkMJAKDkEu1Vo3IlBVwhxCrlcX3gd4KOggCffSUf mlCYGE9F8wNcjoQqx+I4O2w= =TuMH -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message