:> 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
<[EMAIL PROTECTED]>
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
