[Bug 555668] Re: Real-time clock reset breaks boot-time fsck?

[Phillip Susi]

I believe this was fixed some time ago.


** Package changed: util-linux (Ubuntu) => e2fsprogs (Ubuntu)

** Changed in: e2fsprogs (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/555668

Title:
  Real-time clock reset breaks boot-time fsck?

Status in “e2fsprogs” package in Ubuntu:
  Fix Released

Bug description:
  I just had some trouble recovering from a failure in Lucid to handle
  an empty laptop battery; see bugs 555585, 555665.  The salient part is
  that I rebooted with my real-time clock reset to some time in the
  distant past.

  Instead of recovering from this, the boot-time fsck failed and threw
  the boot procedure into the new "fsck failed, what now?" menu.  I'm
  not sure what the right way to handle this situation would be, but one
  wonders if either fsck could ignore "timestamp" problems if it's
  obvious that the clock is wrong (e.g. because it's older than the fsck
  binary) or the boot-time fsck run could somehow force fsck to "fix"
  the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/555668/+subscriptions