#1. Are you sure you got the UUID's correct? #2. Were the filesystems mounted at the time? Fsck won't work on a mounted filesystem; in fact you should have gotten a Big Fat Warning,
Is it checking your filesystem after every boot? And are you paying attention to *which* filesystem it is checking. Are you sure it is checking the filesystems that you just checked by hand? Please check using dumpe2fs -h /dev/hdb1, and note especially these fields: Last mount time: Fri Jul 6 01:51:48 2007 Last write time: Fri Jul 6 01:51:48 2007 Mount count: 2 Maximum mount count: 22 Last checked: Thu Jul 5 22:56:02 2007 Check interval: 15552000 (6 months) Next check after: Tue Jan 1 21:56:02 2008 These should tell the tale about what is going on. It could be any number of things, none of which would be an e2fsprogs bugs. The most likeliest problem is that time is not correctly set at boot. See this bug here: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/43239 But in any case, if you aren't checking the filesystems while they are mounted, check using dumpe2fs after you do the check. That will tell you the state of the filesystem, and whether or not e2fsck will do a check when it runs. Note that if your system clock is not using GMT, definitely take a look at the above referenced above. -- fsck not updating clean history https://bugs.launchpad.net/bugs/125106 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
