Maciej W. Rozycki wrote:
> > Well it's just as much a problem as now. You can already remove a disk
> > after writing it, without unmounting, provided all the data reached the
> > disk. The problem is when you insert the next disk :-)
>
> So what? Unless a disk change detector is damaged (quite unlikely for
> 3.5" drives; I don't think 5.25" are that much used anymore) we already
> know the disk got replaced. As long as further fs writes are disabled
> until a mount there is no problem.
You know, "after disk change notification disable further fs writes"
isn't a bad idea. Along with "disable further fs reads".
I gather forced unmount will be implement soon (it isn't yet), which can
unmount even when an fs is in use. It might make sense to do these
things on a disk change notification:
- Disable further I/O on that mount.
- Forced unmount.
That will help keep the system robust even when the user does silly things.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:22 EST