From owner-freebsd-questions@FreeBSD.ORG  Wed Jan  2 11:27:11 2008
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 944AF16A46C
	for <freebsd-questions@freebsd.org>;
	Wed,  2 Jan 2008 11:27:11 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id DF83C13C46A;
	Wed,  2 Jan 2008 11:27:10 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <477B750E.6060701@FreeBSD.org>
Date: Wed, 02 Jan 2008 12:27:10 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Michael Lednev <liettneff@bk.ru>
References: <782142445.20080102140117@bk.ru> <477B7078.3060404@FreeBSD.org>
	<1337412024.20080102141922@bk.ru>
In-Reply-To: <1337412024.20080102141922@bk.ru>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-questions@freebsd.org
Subject: Re: Panic on umount -f
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2008 11:27:11 -0000

Michael Lednev wrote:
> Hello, Kris.
> 
> On 2 ?????? 2008 ?., 14:07:36 you wrote:
> 
> KK> Yes, long-standing issue with unexpected mounted device removal.  Don't
> KK> do that :)
> 
> Thanks, already found this PR, it's already 5 yo, wow :)
> 

There have been some recent partial workarounds committed in current, 
but this issue is quite difficult to fix completely.

Kris