Comment 3 for bug 423247

Revision history for this message
Jarmo Ilonen (trewas) wrote :

I am not certain if this is the same bug as the reported one, but the symptoms are similar and the ~bug only started happening in karmic this week (around beginning of september 2009). I changed nothing in the configs, just upgraded (it was karmic before, only few days worth of packages).

This is current karmic installed in Virtualbox running in Windows XP. In /etc/default/rcS UTC=yes and the timezone is UTC+3.

After I start virtualbox and boot karmic, everything goes fine. Then I immediately reboot karmic (still running in same Virtualbox instance) and on next reboot it stops when fsck whines:

Superblock last mount time (Thu Sep 3 21:27:09 2009, now = Thu Sep 3 18:31:30 2009) is in the future.

And I have to run fsck manually. Correct time is 18:31, btw.

This is actually quite logical. In first boot Virtualbox gives the hwclock to linux and linux thinks it is in UTC, then adds the time-zone +3. That's where the boot time three hours in the future comes from (21:27 localtime). Later in the boot sequence it gets the correct time from ntp and when the system is rebooted, that value is updated to hwclock, taking UTC setting into account. So on second reboot linux gets the correct time, 15:31 UTC (18:31 localtime).

If I change /etc/default/rcS UTC=no, which is correct because that is what the host OS uses, then karmic in virtualbox works fine on every boot. So arguably in my case this is not a bug, but I still wonder why I never saw that whine from fsck before now.