>> -f The filesystem is forcibly unmounted. Active special devices
>> continue to work, but all other files return errors if further
>> accesses are attempted.
> I think that returning errors is WRONG, unless [...]
> It means that you can't fix the problem with the filesystem and
> resume operations nicely afterwards;
I think I see part of the problem here.
You are thinking "unmount to fix problem, will remount later".
"umount -f" is more like "it's going away, dammit, and I'd rather crash
a few processes than have to take down the whole system".
It might be worthwhile having an option that causes attempted accesses
to hang until the filesystem comes back online, somewhat akin to
Auspex's filesystem "isolation".
der Mouse
[email protected]
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-hackers" in the body of the message
