From owner-freebsd-current Sun Oct 3 13:17:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 3AC4814EE0 for ; Sun, 3 Oct 1999 13:17:27 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id NAA83011; Sun, 3 Oct 1999 13:16:53 -0700 (PDT) From: Archie Cobbs Message-Id: <199910032016.NAA83011@bubba.whistle.com> Subject: Re: panic: free vnode isn't In-Reply-To: from Bob Bishop at "Oct 3, 1999 09:45:43 am" To: rb@gid.co.uk (Bob Bishop) Date: Sun, 3 Oct 1999 13:16:52 -0700 (PDT) Cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Bishop writes: > >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. > > OK, so how do I proceed to get some more useful info? It's still happening. I'd suggest turining off soft-updates first. Then if the panic goes away, at least we have confirmed that soft updates is the likely culprit. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message