[Bug 563618] Re: Ignoring a broken clock results in infinite reboots; not ignoring results in fsck failure; no solution to this problem

[Dave Martin]

Sure, I in no way suggested that my fix was complete :)

A working clock, or synchronising via NTP before checking the rootfs, is the
only full workaround.

However, I would suggest that if broken_system_clock is set, then the target
filesystem should not even be treated as unclean by e2fsck, provided that
all other requirements for cleanness of the filesystem are met--- and should
not be modified at all in this case.  This could solve the problem--- we've
already demonstrated that "fixing" the last mount time in the filesystem is
nonsensical if the clock is invalid anyway.

-- 
Ignoring a broken clock results in infinite reboots; not ignoring results in fsck failure; no solution to this problem
https://bugs.launchpad.net/bugs/563618
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to util-linux in ubuntu.