From owner-freebsd-current@FreeBSD.ORG Wed Sep 29 08:14:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA40916A4CE; Wed, 29 Sep 2004 08:14:13 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CDC743D2D; Wed, 29 Sep 2004 08:14:12 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 37F4A85658; Wed, 29 Sep 2004 17:44:09 +0930 (CST) Date: Wed, 29 Sep 2004 17:44:09 +0930 From: Greg 'groggy' Lehey To: fs@FreeBSD.org, FreeBSD current users Message-ID: <20040929081409.GH20397@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qVHblb/y9DPlgkHs" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Subject: Daily panic in getnewvnode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 08:14:13 -0000 --qVHblb/y9DPlgkHs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline For the last month I've been getting a daily panic out of getvnode. A brief summary: - Panic message is "Cleaned vnode isn't". This means that the vnode pulled off the free list and cleaned with vtryrecycle still has the vp->v_data field set. - It happens during the nightly cron jobs. - The program in question is find, going through a large disk (200 GB, several million files). - The disk does not seem to be getting fsck'd. - The test in question is part of the INVARIANTS checking code, so if I turned INVARIANTS off, the panic would no longer occur. I suspect that if I ran fsck on the disk, it would also solve the problem. The reason I haven't done so is because I chose this particular panic to document for my next kernel debugging tutorial. Unfortunately, I'm running out of time, and I'd really like to find the *real* cause of this bug. If anybody's seen anything like this, please let me know. I have a draft of my tutorial notes at http://www.lemis.com/grog/handout.pdf, and the description starts on page 86. If anybody can help me clarify the problem, I'd be very grateful. Greg -- See complete headers for address and phone numbers. --qVHblb/y9DPlgkHs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBWm7RIubykFB6QiMRAicmAJ9IQHM5Hn6JaUKHykqARalM+XJTLQCfauf+ 2dK6yz7TMrYZCqh7Pmgmnco= =Ca80 -----END PGP SIGNATURE----- --qVHblb/y9DPlgkHs--