aaron kulkis cmiqlkx91hotpopcom carlos f lange wrote anyone else getting annoyed periodic check forced ext3 partitions good thing old days going back unix fsck performed every file system every boot werent periodic forced checks would never fscking filesystems corruption becomes bad 1 notice 2 frustratingly difficult impossible repair without data loss started using ext3 large home partitions recommended opensuse still using reiser smaller raid1 root partition strange bug httpsbugzillanovellcomshow_bugcgiid350992 today passed 60 days limit without checking ext3 wait 10 minutes 200gb partition checked bad enough dont get decent feedback splash splash screen comes hit escape esc key youll get feedback want screen httpsbugzillanovellcomshow_bugcgiid344271 bug imagine unsettling many new users clue happening really question lengthy checks really needed dont want know filesystem corruption past point repaiting guess dont need reiser partition cleared simple journal check isnt journaling systems add fact hard disks becoming bigger forced check times mean one might need wait 20 minutes 12 hour get access machine obviously happen leave 10 minutes print vital document foot hits reset switch use investing lot effort reducing boot time precious seconds give users better linux experience wait 10 minutes fsck every time boot since linux fsck happening every time boot improper shutdowns filesystems marked dirty allows run several months without reboot next kernel patch comes finds corrects filesystem corruption damage still painlessly repairable vented often reboot kcmbjehkulkix uptime 443pm 11 days 1825 83 users load average 415 342 175 kcmbjehkulkix tue 05 aug 2008 083229 0500 opensuse ext3 check forced frustration