From owner-freebsd-current  Sat Oct  2 13:14:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id D420714BF1
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 13:13:50 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from home.elischer.org (home.elischer.org [207.76.204.203])
	by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA02704;
	Sat, 2 Oct 1999 13:13:45 -0700 (PDT)
Date: Sat, 2 Oct 1999 13:13:42 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@home.elischer.org
To: Bob Bishop <rb@gid.co.uk>
Cc: current@FreeBSD.ORG
Subject: Re: panic: free vnode isn't
In-Reply-To: <l0302090db41c18f9f158@[194.32.164.2]>
Message-ID: <Pine.BSF.4.05.9910021312020.45216-100000@home.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Sat, 2 Oct 1999, Bob Bishop wrote:
> >
> >On Sat, 2 Oct 1999, Bob Bishop wrote:
> >
> >> Hi,
> >>
> >> panic: free vnode isn't
> >>
> >> with yesterday's kernel (cvsup Fri Oct  1 04:02:32 BST 1999), on an SMP
> >> system early on in buildworld.
> >>
> >> Skeletal traceback (must get serial console fixed up):

Unfortunatly with this sort of panic, the panic is correct. The actual
dammage was done some (possibly considerable) time before. So a traceback
isn't so useful.


> >>
> >> panic
> >> getnewvnode
> >> ffs_vget
> >> ufs_lookup
> >> ufs_vnoperate
> >> vfs_cache_lookup
> >> ufs_vnoperate
> >> lookup
> >> namei
> >> unlink
> >> syscall
> >>
> >> dmesg etc available on request.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message