Thank you for looking into this. "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."
If I understand correctly, this should be sufficient to consider the originally reported issue "fixed" for e2fsprogs. (It is beyond me why you marked this invalid, as you've actually implemented a check against an insane timestamp, which, essentially, this report was originally about - regardless of what actually caused the misadjusted timestamp. Knowing you're the one who wrote e2fsprogs, though, I won't question your decision here. ;-) Then, as a separate issue, I definitely agree that a standard init process (without e.g. a parallel boot messing things up) shouldn't cause such conditions to occur, where fsck has to (unnecessarily) warn about an "insane clock" (even if the fsck now still runs). (You seem to indicate this has been fixed before you added the task for sysvinit, which would mean we can expect the fix to flow downstream to Ubuntu in due course.) -- 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
