On Sun, Sep 11, 2005 at 01:56:03PM +0200, Helge Kreutzmann wrote:
> (no, I did not change the clock inbetween). So for some reason, the
> last mount time is two hours *in the future*.[1] Two hours reminds me of
> the difference between our daylight saving time (CEST) and UTC.
>
> So there is a bug, maybe the kernel sets the time wrong on mount (just
> guessing). [I verified this on other lvs: always two hours off]
>
> My hardware clock runs on UTC.
More likely /etc/rcS.d/S22hwclockfirst.sh is assuming that your
hardware clock is using localtime, because /etc/default/rcS is
misconfigured. So that sets your time incorrectly for when
/etc/rcS.d/S35mountall.sh runs, but then this gets fixed later on when
ntpdate is run and your time gets set from the network.
In any case, it seems pretty clear this isn't an e2fsprogs bug. I
will keep this bug open however as a reminder to myself that it might
be a good idea to have e2fsck notice when the mount time is in the
future, and print a warning message before fixing it.
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
