From owner-freebsd-fs Mon Dec 9 3:54:23 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E906637B401; Mon, 9 Dec 2002 03:54:21 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-64-169-104-228.dsl.lsan03.pacbell.net [64.169.104.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2100D43E4A; Mon, 9 Dec 2002 03:54:21 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id C541F66BE3; Mon, 9 Dec 2002 03:54:20 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 42C551399; Mon, 9 Dec 2002 03:54:20 -0800 (PST) Date: Mon, 9 Dec 2002 03:54:20 -0800 From: Kris Kennaway To: kirk@mckusick.com, current@FreeBSD.org, fs@FreeBSD.org Subject: panic: getnewvnode: free vnode isn't Message-ID: <20021209115420.GA98392@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline User-Agent: Mutt/1.4i 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 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I just got this on one of my alpha package machines: panic: getnewvnode: free vnode isn't db> trace Debugger() at Debugger+0x34 panic() at panic+0x124 getnewvnode() at getnewvnode+0x434 ffs_vget() at ffs_vget+0xa8 ufs_lookup() at ufs_lookup+0xd68 ufs_vnoperate() at ufs_vnoperate+0x2c vfs_cache_lookup() at vfs_cache_lookup+0x398 ufs_vnoperate() at ufs_vnoperate+0x2c lookup() at lookup+0x4cc namei() at namei+0x300 lstat() at lstat+0x50 syscall() at syscall+0x338 XentSys() at XentSys+0x64 --- syscall (190, FreeBSD ELF64, lstat) --- --- user mode --- --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE99IRrWry0BWjoQKURAqDnAKCIpqLOEl6vio+iDF9D9N/y3ZDo2QCgog65 kuF3KNr1IdZS0SL/ocY4ydo= =0RoF -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Dec 9 11: 1: 7 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AFF437B404 for ; Mon, 9 Dec 2002 11:01:06 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7C1C43E4A for ; Mon, 9 Dec 2002 11:01:05 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gB9J15x3085496 for ; Mon, 9 Dec 2002 11:01:05 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gB9J15x9085484 for fs@freebsd.org; Mon, 9 Dec 2002 11:01:05 -0800 (PST) Date: Mon, 9 Dec 2002 11:01:05 -0800 (PST) Message-Id: <200212091901.gB9J15x9085484@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: fs@FreeBSD.org Subject: Current problem reports assigned to you 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 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- a [2000/10/06] kern/21807 fs [patches] Make System attribute correspon 1 problem total. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Dec 11 9:12:13 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D33937B401 for ; Wed, 11 Dec 2002 09:12:12 -0800 (PST) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 625E643E4A for ; Wed, 11 Dec 2002 09:12:11 -0800 (PST) (envelope-from guptar@cs.rpi.edu) Received: from jenolen.cs.rpi.edu (jenolen.cs.rpi.edu [128.213.12.42]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA96575; Wed, 11 Dec 2002 12:11:47 -0500 (EST) Received: from localhost (guptar@localhost) by jenolen.cs.rpi.edu (8.11.6+Sun/8.9.3) with ESMTP id gBBHBlW19785; Wed, 11 Dec 2002 12:11:47 -0500 (EST) X-Authentication-Warning: jenolen.cs.rpi.edu: guptar owned process doing -bs Date: Wed, 11 Dec 2002 12:11:46 -0500 (EST) From: Rashim Gupta To: Cc: Subject: kernel panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Hi all On compiling a custom kernel I am getting the following error. I am writing a journaled file system and I cannot seem to understand why I keep getting this error. panic: ffswrite: type 0xc1f7fcb8 0 (0,4) Any suggestions what this error might be due to? Also, it is not a persistent error. If I reboot my machine using the same kernel at times I get this error and at times I do not. Thanks in advance Rashim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Dec 11 15: 7:59 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7883A37B401 for ; Wed, 11 Dec 2002 15:07:58 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E54B243EA9 for ; Wed, 11 Dec 2002 15:07:57 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id gBBN7kBF041140; Wed, 11 Dec 2002 18:07:46 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 11 Dec 2002 18:07:46 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Rashim Gupta Cc: fs@freebsd.org, bright@mu.org Subject: Re: kernel panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Wed, 11 Dec 2002, Rashim Gupta wrote: > On compiling a custom kernel I am getting the following error. I am > writing a journaled file system and I cannot seem to understand why I > keep getting this error. Can we assume from this that this error is not occuring in the stock code? > panic: ffswrite: type 0xc1f7fcb8 0 (0,4) > > Any suggestions what this error might be due to? Also, it is not a > persistent error. If I reboot my machine using the same kernel at times > I get this error and at times I do not. Thanks in advance Rashim A casual read of that FFS code shows that the error occurs in ffs_write(), and that it occurs when the vnode type is not an expected or handled type. 0 is probably VNON, so if I had to guess, your vnode has been revoked via revoke() or forceable unmount. Or, the reference count got dropped on the vnode and the memory was recycled for other use, resulting in the type getting zero'd. However, having gotten into the VOP means that (at least recently), the vnode function pointer was pointing at the FFS operation vector rather than the deadfs operation vector. To identify the type of race and/or nastiness, I suggest inspecting the remainder of the vnode structure using a debugger. Check the current reference counts, value of the operation vector pointer, lock information, etc. There is a known race involving deadfs and revoke() that could be at work, but it could easily also be a local race condition involving reference counts. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message