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

[Oliver Grawert]

even with broken_system_clock the infinite reboot occurs on first boot ... 
one thing we came up with during the discussion is to probably capture the last mount time from the filesystem in the initramfs and then set the clock to this value before mountall runs we will probably have a session about this at UDS to discuss the several workarounds we see, teh bug in itself is unsolvable unless we start using non journalled filesystems

-- 
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.