From owner-freebsd-bugs@FreeBSD.ORG  Thu May 22 20:36:00 2008
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3E2EF1065672;
	Thu, 22 May 2008 20:36:00 +0000 (UTC) (envelope-from vwe@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 2CD008FC14;
	Thu, 22 May 2008 20:36:00 +0000 (UTC) (envelope-from vwe@FreeBSD.org)
Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4MKa0bc027726;
	Thu, 22 May 2008 20:36:00 GMT
	(envelope-from vwe@freefall.freebsd.org)
Received: (from vwe@localhost)
	by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4MKZxqr027722;
	Thu, 22 May 2008 20:35:59 GMT (envelope-from vwe)
Date: Thu, 22 May 2008 20:35:59 GMT
Message-Id: <200805222035.m4MKZxqr027722@freefall.freebsd.org>
To: nejc@skoberne.net, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: vwe@FreeBSD.org
Cc: 
Subject: Re: kern/123908: panic: vinvalbuf: dirty bufs
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2008 20:36:00 -0000

Synopsis: panic: vinvalbuf: dirty bufs

State-Changed-From-To: open->closed
State-Changed-By: vwe
State-Changed-When: Thu May 22 20:29:59 UTC 2008
State-Changed-Why: 

Nejc,
I'm really sorry to do what I have to do now...
I really understand the situation isn't nice and you may have already wasted
some hours to find a solution to your problem, but you've hit 1) a well known
problem and 2) could have been able to find already _a lot_ problem reports
being filed about panics caused by pulling an active device.
Please do not pull a storage device while it holds active mounts. I'm pretty
sure you would never pull your CPU while it's doing some calculations for you,
would you? ;)
Please understand while a device is holding active mounts, there are buffers
allocated pointing to your device. Also there's filesystem information still
in RAM which may not already have been written to the storage device. Be sure
you may loose data if pulling an active device out of your system.
For the next real, not already known problem, please keep in mind, we need
a stack backtrace from the moment when the panic has been fired.
Thank you for your understanding.

http://www.freebsd.org/cgi/query-pr.cgi?pr=123908