volume management

[Tomas Zvala]

Eric Anderson wrote:
>
> I think the only time this might even be an option is under very 
> minimal conditions.  As Pawel said, if your FS is corrupt, you'll get 
> hosed down the line.
>
> Personally, what I would want to prevent, is having a server go down 
> due to one file system having an issue, when it is serving (or using) 
> many more file systems.  I currently have a box with 5 10Tb file 
> systems on it, and when I mount a 6th file system (2Tb) which I *know* 
> has metadata inconsistencies that fsck can't fix, I don't want it to 
> take down all 50Tb of good solid storage.  What I want is a blast to 
> my logs, the erroneous file system to be evicted from further damage 
> (mount read-only and marked as dirty) and trickle an i/o error to any 
> processes trying to write to it.  Even unmounting it would be ok, but 
> that gets nasty with NFS servers and other things.
>
>
> Eric
>
This might as well be a dumb question... But  ... Why don't we let the
root choose, what is supposed to happen? That makes most sense to me and
even though i'm no fbsd hacker, it seems to me as not a big deal to
implement.


Tomas