On 2011-04-01 19.03, Amit Kulkarni wrote:
> Thank you Arthur and the team for a very fast turnaround! Thank you
> for reducing the pain. I will schedule a fsck every month or so,
> knowing it won't screw up anything and be done really quick.
Why "schedule" fsck runs at all? The file system code is very mature and
although of course it would be unwise to declare it bug free, I see very
little reason to run fsck on a file system unless there have been some
problem like an unclean shutdown to prompt it (in which case of course,
the system does it for you automatically when rebooting).
I've noticed that some (all?) linux systems do uncalled-for file system
checks at boot if no check have been made recently, but I've never
understood this practice. It must mean they don't trust their own file
systems, which frankly I find a bit unsettling... I'd rather use a file
system that's been field proven for decades than use something thats
just come out of the experimenting shop.
Regards,
/Benny
--
internetlabbet.se / work: +46 8 551 124 80 / "Words must
Benny Lvfgren / mobile: +46 70 718 11 90 / be weighed,
/ fax: +46 8 551 124 89 / not counted."
/ email: benny -at- internetlabbet.se
