Date: Thu, 19 Jul 2007 08:51:01 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: idiotbg@gmail.com Cc: josh@tcbug.org, linimon@lonesome.com, freebsd-stable@FreeBSD.org, LoN_Kamikaze@gmx.de Subject: Re: removing external usb hdd without unmounting causes reboot? Message-ID: <20070719.085101.-1860900987.imp@bsdimp.com> In-Reply-To: <200707181942.45045.idiotbg@gmail.com> References: <20070718170559.GA11915@eos.sc1.parodius.com> <20070718173406.GA16748@soaustin.net> <200707181942.45045.idiotbg@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200707181942.45045.idiotbg@gmail.com>
Momchil Ivanov <idiotbg@gmail.com> writes:
: On Wednesday 18 July 2007 19:34:06 Mark Linimon wrote:
: > On Wed, Jul 18, 2007 at 10:05:59AM -0700, Jeremy Chadwick wrote:
: > > Bottom line here is that the kernel panics when removing a USB device
: > > that has filesystems mounted.
: >
: > s/USB //
:
: Just a dumb question: what does "umount -f" does? And doing something like
: that when a fs goes away shouldn`t fix it?
It won't fix it. The problem is dangling pointers to devices that no
longer exist. And like all dangling references after 'free' you get
bad thing happening.
: If the problem is in general with a file system, regardless of the provider,
: then what does one do when a mounted smbfs becomes unavailable due to remote
: host down, no route to host or some other network related problems? Same
: question for NFS mounted filesystems?
In those cases, the device doesn't go away. Just the remote host.
This is a big difference.
Believe me, if it were easy, it would have been fixed. If it was
moderate to fix, it would have been fixed. It is a hard problem that
people have put lots of hours into to try to resolve. To imply
otherwise is really insulting to all those people (myself include)
that have tried to fix this.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070719.085101.-1860900987.imp>