fsck on every reboot due to superblock having future date

Hi,

Subscribing Scott who is the expert on these bugs.

Could you please provide the output of

    date
    grep UTC /etc/default/rcS
    hwclock --debug --show

that will give the basic information that is needed.

Thanks,

James

roland@logikaldesktop:~$ date
Fri Sep 18 10:40:35 CDT 2009
roland@logikaldesktop:~$ grep UTC /etc/default/rcS
UTC=no
roland@logikaldesktop:~$ hwclock --debug --show
hwclock from util-linux-ng 2.16
Using /dev interface to clock.
Last drift adjustment done at 1253248008 seconds after 1969
Last calibration done at 1253248008 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2009/09/18 10:40:53
Hw clock time : 2009/09/18 10:40:53 = 1253288453 seconds since 1969
Fri 18 Sep 2009 10:40:53 AM CDT -0.526146 seconds
roland@logikaldesktop:~$

Keep in mind this is after I've cleaned up everything during boot. I will
print out your email and try to run the commands the next time I boot and
everything is trashed. Don't know how I will save the output exactly since it
is a rescue mode console I have to work with.

On Friday 18 September 2009 05:13:45 am James Westby wrote:
> Hi,
>
> Subscribing Scott who is the expert on these bugs.
>
> Could you please provide the output of
>
> date
> grep UTC /etc/default/rcS
> hwclock --debug --show
>
> that will give the basic information that is needed.
>
> Thanks,
>
> James
>
>
> ** Changed in: kpackagekit (Ubuntu)
> Status: New => Incomplete
>
> ** Summary changed:
>
> - [karmic] today's 174 updates trash system clock
> + fsck on every reboot due to superblock having future date
>

--
Roland Hughes, President
Logikal Solutions
(630)-205-1593 (cell)
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.logikalsolutions.com

As of today, one of the update sets which came out seems to have fixed this. There is still a lot of fall out with the problems it created, but the clock/future date problem at boot up seem to be gone.

Thanks for the update. I am closing this bug as "Invalid" as we don't know
exactly what fixed it. Please re-open the bug if the problem comes back.

Thanks,

James

I still have this bug even after today system update. The superblock mount date is periodically set in the future for <my timezone offset>-1 hour.

It seems to be tied to the LS-120 bug. Whever the date/time work, so do the
LS-120 drives.

On Wednesday 23 September 2009 01:49:14 pm AsstZD wrote:
> I still have this bug even after today system update. The superblock
> mount date is periodically set in the future for <my timezone offset>-1
> hour.
>
> ** Changed in: kpackagekit (Ubuntu)
> Status: Invalid => New
>

--
Roland Hughes, President
Logikal Solutions
(630)-205-1593 (cell)
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.logikalsolutions.com

Status changed to 'Confirmed' because the bug affects multiple users.