From owner-freebsd-current@FreeBSD.ORG  Fri Aug  8 06:24:13 2003
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 021C537B401
	for <freebsd-current@freebsd.org>;
	Fri,  8 Aug 2003 06:24:13 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ED12E43F3F
	for <freebsd-current@freebsd.org>;
	Fri,  8 Aug 2003 06:24:11 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h78DO91f008939;
	Fri, 8 Aug 2003 15:24:09 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: "Aaron Wohl" <freebsd@soith.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 08 Aug 2003 07:09:12 MDT."
             <20030808130912.A429138CCB@www.fastmail.fm> 
Date: Fri, 08 Aug 2003 15:24:09 +0200
Message-ID: <8938.1060349049@critter.freebsd.dk>
cc: freebsd-current@freebsd.org
Subject: Re: vinum lock panic at startup -current 
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: Fri, 08 Aug 2003 13:24:13 -0000

In message <20030808130912.A429138CCB@www.fastmail.fm>, "Aaron Wohl" writes:

>  Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198

Ok, then I think I know what it is.

Vinum appearantly does not go through SPECFS but rather calls into
the disk device drivers directly.  That is a pretty wrong thing to
do, and it seems that vinum does not respect the D_NOGIANT
flag which GEOM recently started setting.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.