The fundamental bug here is in the init scripts. E2fsck assumes that
the system time is correct. Unfortunately, if you have the system time
set to tick localtime, instead of GMT, the Debian/Ubuntu boot scripts do
not adjust for the fact that the hardware clock is not ticking UTC until
after checking the root filesystem. This causes the "last checked"
time to be writen out in the wrong time zone, and then if you reboot
right away, it causes this problem.
In the latest versions of e2fsprogs, e2fsck will print a messaging that
the clock is insane, and then check the filesystem since it could also
be the case that the clock is insane. But the real, fundamental flaw
is that the init scripts aren't correctly making sure that the system
clock is accurately set before e2fsck is run.
** Changed in: e2fsprogs (Ubuntu)
Status: Confirmed => Invalid
** Also affects: sysvinit (Ubuntu)
Importance: Undecided
Status: New
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
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
