Hi,

Greg Oster writes:
 > > > One fsck doesn't always find all the problems.  If you have a really
 > > > nasty crash, multiple "fsck -f"'s might be needed before fsck 
doesn't
 > > > find any further errors.  Just because you did one fsck doesn't mean
 > > > it fixed all the problem!  (I wouldn't go blaming RAIDframe if you
 > > > just did a single fsck after a nasty crash.)
 > >
 > > Shouldn't /etc/rc.d/fsck handle this? That is, to run fsck up to
 > > $fsck_max_runs times unless it succeeds?
 >
 > I think with the way fsck runs from /etc/rc.d is that if it encounters
 > certain serious errors that it punts, and forces an admin to run fsck
 > by hand.  It's getting the admin to run fsck a couple of times that
 > could be the hard part...

maybe there should be some fsck flag to force fsck to leave the 
filesystem really clean? What about -l (as loop)?

I use fsck_flags=-y in rc.conf on some machines where I probably would 
like to use -yl ...

r.