From owner-freebsd-current@FreeBSD.ORG  Wed Mar  3 10:02: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 2663E16A4CE
	for <current@freebsd.org>; Wed,  3 Mar 2004 10:02:59 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 495B143D1D
	for <current@freebsd.org>; Wed,  3 Mar 2004 10:02:58 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i23I2pvO008349;
	Wed, 3 Mar 2004 19:02:56 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Christian Brueffer <chris@unixpages.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Wed, 03 Mar 2004 17:25:02 +0100."
             <20040303162502.GA26422@unixpages.org> 
Date: Wed, 03 Mar 2004 19:02:51 +0100
Message-ID: <8348.1078336971@critter.freebsd.dk>
cc: current@freebsd.org
Subject: Re: panic: Consumer with zero access count in g_dev_strategy 
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, 03 Mar 2004 18:02:59 -0000

In message <20040303162502.GA26422@unixpages.org>, Christian Brueffer writes:
>
>got the following panic while doing a forced umount and detach of gbde
>encrypted IDE disc.

Forced umounts are in a sorry state (I'm not convinced they ever were in
a much better state actually) and we need to overhaul that aspect of
the buffer cache in the future.

I guess another way to say this is "don't do that then"

-- 
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.