On Saturday, January 19, 2002 10:46:09 AM +0100 Russell Coker
<[EMAIL PROTECTED]> wrote:
> USB by it's nature is something external to the system. Unplugging a USB
> cable with a mounted drive attached should (IMHO) get the same result as
> unplugging an Ethernet cable with an NFS mount in progress. This means
> processes go into D state if they have outstanding writes, and for reads
> they may go D state depending on mount options, and then you wait for
> the device to become available again.
>
> For a file system on USB ReiserFS would have to recheck the superblock
> (to make sure that it hasn't been mounted on another computer in the
> mean time) before allowing access again. Also there would have to be a
> recovery process for the situation when the USB device is gone for good.
suspending until the device is available again is best done below the
filesystem level. The block layer really should be able to pause things
until the device goes back in (with an umount -f to clean up).
2.5.x might have better reactions here, we'll have to wait and see.
Of course, if by handle removable storage you mean doesn't trigger an oops,
that is #2 on my list after ordered writes.
-chris
