On 17/04/10 05:41, Andy Smith wrote:
Would it bother you if you one day discovered that
time-based fsck
had been disabled for you without your knowledge since you aren't on
this mailing list?
It probably would actually - even though ext3 rarely goes wrong it has
happened to me a couple of times before.
It could be possible to take a leaf out of the cicada's book and set the
time / mount count to primes (7/31 maybe?) to help things along - and I
don't know if you keep stats on how often users reboot their VMs (you'd
hope more than once a year) but if so setting the time to some point in
the 60-70% percentile or something would improve things without getting
rid of the checking altogether.
You could always mail customers directly and have them deliberately turn
it back on if they want it, but I would imagine people will care much
more after the fs goes wrong and they remember checking was off at some
point a year or so from now ;)
Cheers
Alex.
--
This message was scanned by Better Hosted and is believed to be clean.
http://www.betterhosted.com