Comment 41 for bug 427822
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote Re: fsck says last write time in future | #41 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Indeed, jaunty had a switch to fsck to "automatically repair" that issue - upstream put it there claiming we had buggy init scripts.
We took it out because we're damned sure our scripts are right (the fact the "now" time is always correct when you hit the fsck shell confirms that), and wanted to see what other bugs were underneath.
Enough duplicates of this issue now appear, which after debugging turn out to be local configuration issues, hardware clock reliability issues, virtualisation issues, and simple human error issues, that I'm convinced that "automatic repair" is the right way forward.
I'll be patching e2fsck today to fix that issue with -a again