Date: Tue, 31 Jul 2007 22:43:27 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Dennis Melentyev" <dennis.melentyev@gmail.com> Cc: peterjeremy@optushome.com.au, freebsd-stable@freebsd.org, dennis.melentyev@gmail.com Subject: Re: removing external usb hdd without unmounting causes reboot? Message-ID: <200708010543.l715hRkV075424@apollo.backplane.com> References: <20070727231905.GJ1152@turion.vk2pj.dyndns.org> <200707301319.l6UDJkAH068637@lurza.secnetix.de> <b84edfa10707301123t1e45e233t9c0f195afcb65c2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:> By the way, the problem apparently has been solved in
:> DragonFly BSD (i.e. DF BSD does not panic when a mounted
:> FS is physically removed). Maybe it is worth to have a
We didn't do much here. Just started pulling devices, looking at the
crash dumps, and fixing things.
Basically it was just a collection of minor bugs... things like certain
error paths in UFS (which only occur on an I/O error) had bugs, or
caused corruption instead of properly handling the error, and
various bits and pieces of the USB I/O path would get ripped out on
the device pull while still referenced by other bits of the USB I/O
path.
You will also have to look at the way vfs flushing handles errors
in order to allow a filesystem to be force-unmounted after the device
has been pulled. Basically you have to make umount -f work and you have
to make sure it properly dereferencing the underlying device and properly
destroys the (now unwritable) dirty buffers.
-Matt
Matthew Dillon
<dillon@backplane.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200708010543.l715hRkV075424>