Date: Wed, 29 Sep 2004 17:44:09 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: fs@FreeBSD.org, FreeBSD current users <FreeBSD-current@FreeBSD.ORG> Subject: Daily panic in getnewvnode Message-ID: <20040929081409.GH20397@wantadilla.lemis.com>
next in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040929081409.GH20397>