Date: Thu, 22 May 2008 20:35:59 GMT From: vwe@FreeBSD.org To: nejc@skoberne.net, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/123908: panic: vinvalbuf: dirty bufs Message-ID: <200805222035.m4MKZxqr027722@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200805222035.m4MKZxqr027722>