correcting system time leads to unbootable system
Bug #457478 reported by
Chris Jones
This bug report is a duplicate of:
Bug #268808: superblock last write time is in the future.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mountall (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: mountall
I encountered a laptop which was installed today via a USB stick with late alpha or beta of karmic in an entirely offline way.
I plugged it into a network for the first time and it presumably NTP'd itself to the correct time.
The next reboot refused to boot because the system clock had gone back in time and so the previous mount time was in the future.
Given the feeble nature of clocks in PCs, why are we caring at all about the previous mount time?
Revision history for this message
| Chris Jones (cmsj) wrote | #1 |
Revision history for this message
| Chris Jones (cmsj) wrote | #2 |
To post a comment you must log in.
Should this actually be filed against fsck?