hello everyone. i guess this has been asked before, but haven't found it in the faq. i have the following issue... it is not uncommon nowadays to have desktops with filesystems in the order of 500gb/1tb. now, my kubuntu (but other distros do the same) forces a fsck on ext3 every so often, no matter what. in the past it wasn't a big issue. but with sizes increasing so much, users are now forced to wait for several minutes (every so often) for their desktops to boot up. to the point that the thing has become unacceptable. i know i can tune/disable this, but i'd like to understand once and for all what is the technical rationale behind this practice and what use is there to force a fsck on a clean fs... i must be missing something... :-( thanks in advance. cheers.
> i know i can tune/disable this, but i'd like to understand once > and for all what is the technical rationale behind this practice > and what use is there to force a fsck on a clean fs...Disks rot. -- --- Larry McVoy lm at bitmover.com http://www.bitkeeper.com
giancarlo corti wrote:> hello everyone. > > i guess this has been asked before, but haven't found it in the faq. > > i have the following issue... > > it is not uncommon nowadays to have desktops with filesystems > in the order of 500gb/1tb. > > now, my kubuntu (but other distros do the same) forces a fsck > on ext3 every so often, no matter what.Did you just update to e2fsprogs-1.40.3? If so, should be fixed in 1.40.4 for the most part. See Debian bug 454926, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454926 -Eric