From owner-freebsd-current@FreeBSD.ORG  Sat Jul 10 01:05:59 2004
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 43D1F16A4CE
	for <current@freebsd.org>; Sat, 10 Jul 2004 01:05:59 +0000 (GMT)
Received: from imf18aec.mail.bellsouth.net (imf18aec.mail.bellsouth.net
	[205.152.59.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A5BFF43D1D
	for <current@freebsd.org>; Sat, 10 Jul 2004 01:05:58 +0000 (GMT)
	(envelope-from ahze@ahze.net)
Received: from [192.168.1.5] ([68.209.163.3])
	by imf18aec.mail.bellsouth.netESMTP
	<20040710010558.DYLG1776.imf18aec.mail.bellsouth.net@[192.168.1.5]>
	for <current@freebsd.org>; Fri, 9 Jul 2004 21:05:58 -0400
Mime-Version: 1.0 (Apple Message framework v618)
Content-Transfer-Encoding: 7bit
Message-Id: <4D52DE9C-D20D-11D8-8E97-000A958C81C6@ahze.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: current@freebsd.org
From: michael johnson <ahze@ahze.net>
Date: Fri, 9 Jul 2004 21:05:58 -0400
X-Mailer: Apple Mail (2.618)
Subject: Vinum and freebsd
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: Sat, 10 Jul 2004 01:05:59 -0000

Hi,
	I've had problems with vinum and newer 5.2-CURRENT kernels, I am 
unable to boot a newer kernel with out the kernel going in to a panic 
and saying "panic: umount: dangling vnode" . I've had this problem 
since early June and it doesn't seemed to be fixed (as of July 9th) , 
has something changed in vinum that I am missing and I need to change 
about my setup or is vinum just broken right now?

The vinum setup I have right now is pretty old and should I have to 
rebuild it?

Michael