From owner-freebsd-current@FreeBSD.ORG  Wed Jan 12 21:17:54 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 73C3316A4D5
	for <freebsd-current@freebsd.org>;
	Wed, 12 Jan 2005 21:17:54 +0000 (GMT)
Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com
	[209.20.186.192])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4089B43D49
	for <freebsd-current@freebsd.org>;
	Wed, 12 Jan 2005 21:17:54 +0000 (GMT)	(envelope-from randy@psg.com)
Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com)
	by ran.psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CopsF-000Eke-Cm; Wed, 12 Jan 2005 13:17:51 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16869.37886.885177.826496@ran.psg.com>
Date: Wed, 12 Jan 2005 13:17:50 -0800
To: Doug White <dwhite@gumbysoft.com>
References: <16860.4383.281114.747270@roam.psg.com>
	<20050110183217.M84532@carver.gumbysoft.com>
cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: fsck issue?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2005 21:17:54 -0000

> These backtraces are generated by this code in getdirtybuf():
> 5847                 if (bp->b_vp == NULL)
> 5848                         kdb_backtrace();
> 
> Somehow there's a buf floating around without a vnode attached. I'd
> suggest booting single user and fsck -y'ing all your filesystems to verify
> there is no residual damage, and remove any snapshots from your ufs2
> filesystems.

been doing that, except for snap removal.  do you mean 
   rm -rf /foo/.snap/*
?

randy