Activity log for bug #268808

Date Who What changed Old value New value Message
2008-09-11 01:30:13 Sid MacT bug added bug
2008-09-11 01:31:21 Sid MacT description 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 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. 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 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.
2008-09-11 01:37:26 Sid MacT description 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 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. 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.
2009-01-13 00:22:03 Andres Mujica None: bugtargetdisplayname Ubuntu sysvinit (Ubuntu)
2009-01-13 00:22:03 Andres Mujica None: bugtargetname ubuntu sysvinit (Ubuntu)
2009-01-13 00:22:03 Andres Mujica None: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in SYSVINIT. For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.
2009-01-13 00:22:03 Andres Mujica None: title Bug #268808 in Ubuntu: "superblock last write time is in the future" Bug #268808 in sysvinit (Ubuntu): "superblock last write time is in the future"
2009-10-02 08:49:49 Stefan Hamminga bug task added ubiquity
2009-10-02 09:31:30 Colin Watson bug task added ubiquity (Ubuntu)
2009-10-02 09:32:42 Colin Watson ubiquity: status New Invalid
2009-10-04 01:11:29 GaTechGrad attachment added Superblock last mount time is in the future on Sun VirtualBox http://launchpadlibrarian.net/32959060/ubuntu_boot_bug.png
2009-10-12 12:09:06 Scott James Remnant (Canonical) affects sysvinit (Ubuntu) e2fsprogs (Ubuntu)
2009-10-12 12:09:37 Scott James Remnant (Canonical) e2fsprogs (Ubuntu): status New Triaged
2009-10-12 12:09:43 Scott James Remnant (Canonical) e2fsprogs (Ubuntu): importance Undecided High
2009-10-12 12:09:48 Scott James Remnant (Canonical) e2fsprogs (Ubuntu): assignee Scott James Remnant (scott)
2009-10-12 12:09:55 Scott James Remnant (Canonical) nominated for series Ubuntu Karmic
2009-10-12 12:09:55 Scott James Remnant (Canonical) bug task added e2fsprogs (Ubuntu Karmic)
2009-10-12 12:09:55 Scott James Remnant (Canonical) bug task added ubiquity (Ubuntu Karmic)
2009-10-12 12:10:09 Scott James Remnant (Canonical) e2fsprogs (Ubuntu Karmic): milestone ubuntu-9.10
2009-10-12 16:00:13 Launchpad Janitor e2fsprogs (Ubuntu Karmic): status Triaged Fix Released
2009-10-23 19:32:02 Brian Murray ubiquity (Ubuntu Karmic): status New Invalid
2009-12-05 08:03:36 Launchpad Janitor branch linked lp:ubuntu/e2fsprogs
2010-05-28 16:57:04 Julian Wiedmann removed subscriber Julian Wiedmann