Dude, That's 134 Years

I have a hunch that the hardware clock is off on this host…

…but by 134 years into the future?

I didn’t actually get to see what it was set to, as the machine fixed itself via NTP shortly afterwards. I suspect the last mount time is some sort of unsigned integer that overflowed.

Of course, on the subsequent reboot it needed to check the filesystems yet again, putting the last checked time back to normal.

2 thoughts on “Dude, That's 134 Years”

  1. ntpd (actually ntpdate in this case I expect as it’s at boot and to allow the large jump) usually writes how much it changes the clock by with syslog, so you can see if it really was 134 years out that way 🙂

Comments are closed.