Public bug reported:
When /etc/default/rcS has the line
UTC=no
then when Ubuntu startup runs fsck one receives the message:
'superblock last write time is in the future. FIXED'
googling reveals the problem is the hardware clock is set to local time,
but the Ubuntu shutdown process writes the UTC, i.e., GMT time to the
superblock.
So on reboot, when the fsck compares the hardware clock to the superblock,
the GMT time in the superblock is 'in the future'.
Note: my time zone is California, so GMT is 7 or 8 hours ahead of my
local time.
All the google links talk about the problem being that the startup process does
the
superblock compare, via fsck, before the routine runs that resets the system
time.
My perception is that the real issue is that the shut-down scripts write the
GMT time to
the superblock instead of the local time.
I know there is the work-around of setting UTC=yes; but this messes up
people the dual-boot(ugh) Windows.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: fsck superblock utc
** Description changed:
When /etc/default/rcS has the line
UTC=no
then when Ubuntu startup runs fsck one receives the message:
'superblock last write time is in the future. FIXED'
googling reveals the problem is the hardware clock is set to local time,
but the Ubuntu shutdown process writes the UTC, i.e., GMT time to the
superblock.
So on reboot, when the fsck compares the hardware clock to the superblock,
the GMT time in the superblock is 'in the future'.
All the google links talk about the problem being that the startup process
does the
superblock compare, via fsck, before the routine runs that resets the system
time.
- My perception is that the real issue is that the shut-down routing writes the
GMT time to
+ My perception is that the real issue is that the shut-down scripts write the
GMT time to
the superblock instead of the local time.
I know there is the work-around of setting UTC=yes; but this messes up
people the dual-boot(ugh) Windows.
** Tags added: fsck superblock utc
** Description changed:
When /etc/default/rcS has the line
UTC=no
then when Ubuntu startup runs fsck one receives the message:
'superblock last write time is in the future. FIXED'
googling reveals the problem is the hardware clock is set to local time,
but the Ubuntu shutdown process writes the UTC, i.e., GMT time to the
superblock.
So on reboot, when the fsck compares the hardware clock to the superblock,
the GMT time in the superblock is 'in the future'.
+ Note: my time zone is California, so GMT is 7 or 8 hours ahead of my
+ local time.
+
All the google links talk about the problem being that the startup process
does the
superblock compare, via fsck, before the routine runs that resets the system
time.
My perception is that the real issue is that the shut-down scripts write the
GMT time to
the superblock instead of the local time.
I know there is the work-around of setting UTC=yes; but this messes up
people the dual-boot(ugh) Windows.
--
superblock last write time is in the future
https://bugs.launchpad.net/bugs/268808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
