>What I notice is that the last checked time doesn't seem to be getting updated. It shows Jan 1, 1970 - even though if just ran through fsck 30 minutes ago, and every >time I boot.
In humandoing's case, it looks like the problem is that the battery for his CMOS system clock is dead, so the time is always incorrectly set at Jan 1, 1970 during early boot. That a separate problem, and about the only fix would be for e2fsck to never do time-based checks if someone has bad hardware clock on their system. So unliike dahas's comment, the solution would be for e2fsck it *ignore* the tune2fs settings, because the system clock can't be trusted when e2fsck is run. -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 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
