I was wondering if solving the problem was worth while, or whether we'd be better of just scrapping the check altogether, so a while ago I asked a couple of ext3 devs:
Does fsck need to be run on ext3 partitions? Andrew Morton: Theoretically: no. Practically: yes. There are software bugs and hardware bugs and things can go wrong on-disk. You want to catch them early. Personally I disable the auto-fsck thing and I'll run fsck manually once or twice a year, when the time suits me. Mingming Cao: Periodically fsck ext3 is still needed, even if ext3 is a journalled fs. kernel code vm/fs could be buggy, or disks IO errors, which cause filesystem metadata corrupted silently, this can't be detected by simply replaying the journal log. Well how often should ext3 do the sanity check is really depend on the customer's priority, whether they would like to trade some of the boot up time with more confident of the fs's healthy. It's probably a good idea to warning the user that the scheduled fsck is coming and let user to decide whether they want to do it or delaying it. -- New ext3 partitions should not have max-mount count https://bugs.launchpad.net/bugs/3581 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
