** Description changed: If the system clock has been misadjusted while fsck last run, fsck reports on next boot that the partition "has gone 49710 days without being checked, check forced". Happens to me in Ubuntu after I do an occasional boot to a parallel partition if fsck gets run there. This is clearly nonsense. A quick google of "fsck 49710" gives out numerous examples, revealing inter alia that 49710 days is close to 2^32 seconds, and gives a clear indication that fsck simply isn't equipped to deal with a misconfigured system clock. In such a case fsck should only run if the filesystem was actually marked "dirty", i.e. not just because of the old timestamp. In addition, fsck probably could fix the timestamp. - - The problem is annoying. It often occurs for me when I try to debug various system configuration issues (mainly X). Sometimes the system hangs, leading to a hard boot, leading to fsck, often leading to the further aggravation of unnecessary fsck checks due to a 136-year old timestamp. + The problem is annoying. It often occurs for me when I try to debug + various system configuration issues (mainly X). Sometimes the system + hangs, leading to a hard boot, leading to fsck, often leading to the + further aggravation of unnecessary fsck checks due to a 136-year old + timestamp.
-- 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
