You are not logged in.
A few days ago I started to get the message:
'Superblock last write time is future'
every time I boot. This is happening for all of my partitions on both of my hard drives. I also received a message that all of my partitions haven't been checked in 5480 days and the subsequent file system check happened once. These things started within the last week and I have no idea what's causing it. At first I thought that maybe it was a kernel upgrade, but downgrading didn't help. Any ideas?
By the way, this is an Arch x86_64 box.
Offline
Check the time in your BIOS.
Offline
It's a race! The time in my BIOS is almost exactly what the time on my satellite clock is. What you said may have led me to the culprit: I just re-installed OpenNTPD this week. If my BIOS is almost real-time, and OpenNTPD is suffering from network lag...
What do you think?
Offline
Maybe. I would think there'd have to be an awful lot of lag though.
Offline
Probably the year is wrong?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
I have this same error message on 2 systems running arch. I think the messages started after updating e2fsprogs a couple of days ago. I don't get the error messages every time the system is booted-maybe 50% of the time.
Offline
I have the same problem and I believe I know the cause.
I have my bios clock set at local time, because I dual boot with Windows. Now I've learned that ext3 saves it's write times in UTC, regardless of the bios clock. Studying the arch boot scripts, I found that all local filesystems are mounted before the system clock is configured. Meaning that at the moment of mounting the filesystems, the bios clock is used.
Now remember that the bios clock set at local time, and the filesystem is set at UTC. So in my case, my time zone is GTM-8. This means that if it's 10:00 local time and I reboot my PC, the last write time in the superblock is set at 18:00. Now, when the system boots up, it'll read the time from the bios clock (let's say 10:02), the init scripts try to mount the filesystems, and find that the superblock has a last write time of 18:00, efectively, the future.
Well, that's my theory atleast. I'll move around stuff in the initscripts and see if I'm right first, before I report this on the bug tracker.
Offline
Changed my hardware clock to the top of rc.sysinit, but now it wants to write 0.0 0 0.0 to a file called /var/lib/hwclock/adjtime (it was a conditional [[ ! -f ]] so that it would only happen if the file didnt exist and it does, at least I believe nothing deletes it). As I have /var in another partition it complains. So i deleted those lines. Can that turn out to be a problem?
----
Marcio
Offline
I'm getting these same errors myself and I'm guessing it's one thing or the other. I recently installed OpenNTPD and noticed that someone said they noticed the errors showing up after installing it. After some googling, it looks like other people are getting these same errors from a recent version of e2fsprogs.
Offline
I'm still getting this errors and don't use Open NTPD. After googling i found in Ubuntu had the same problem. It is suposed to be something with the boot scripts, i don't know. I used reiser4 before with no problem, but 3 weeks ago i had to reinstall arch and haven't turn it to reiser4 yet...
All your base are belong to us
Offline
When I switched over to 'UTC' in my rc.conf file (as suggested earlier in this thread), it stopped the behavior most of the time. It never completely stopped though.
Offline
This seems to happen for me only on a reboot, not when I shut down over night. This seems to suggest that the "write time in the future" is not too far in the future. I am using openntp and I have the time set to UTC in rc.conf. The error doesn't seem to matter, although it is always nice to not see anything like this during boot
Offline
Any further news on this problem. I am using local time as well due to dual.....triple booting lol. Anyway, my laptop uses reiserfs and I do not have this problem. My desktop is using ext.3 and does have the problem.
thanks,
McRae
Offline
Changed my hardware clock to the top of rc.sysinit, but now it wants to write 0.0 0 0.0 to a file called /var/lib/hwclock/adjtime (it was a conditional [[ ! -f ]] so that it would only happen if the file didnt exist and it does, at least I believe nothing deletes it). As I have /var in another partition it complains. So i deleted those lines. Can that turn out to be a problem?
See these bugs:
#5529, #5444 (fixed in testing/initscripts-0.7.3-1),
#5445.
to live is to die
Offline
i'm having this problem after a recent install, too. i tried this fix in 5529 so far, which didn't work for me:
The real fix is to move
if [ "$TIMEZONE" != "" ]; then
/bin/ln -sf /usr/share/zoneinfo/$TIMEZONE /etc/localtime
fi
before
if [ "$HARDWARECLOCK" = "UTC" ]; then
haven't tried the initscripts in testing yet.
Offline
i'm having this problem after a recent install, too. i tried this fix in 5529 so far, which didn't work for me
This change should be made during installing process, before first reboot.
to live is to die
Offline
okay, i guess it's on to the testing initscripts then.
Offline
I'm still getting the "future error message", even when i have a testing box. It actually never disappeared. Consequently, bug 5445 is still open, but i don't see any advance with it. Do someone know something?
All your base are belong to us
Offline
I'm still getting the "future error message", even when i have a testing box. It actually never disappeared. Consequently, bug 5445 is still open, but i don't see any advance with it. Do someone know something?
Try to edit rc.sysinit - remove lines where it symlinks /etc/localtime and just copy the required file to /etc/localtime.
Report back here and to BT if this fixes your problem.
(I don't have such issues so I cannot do testing).
to live is to die
Offline
Nope, it didn't work
All your base are belong to us
Offline
Nope, it didn't work
Does moving instructions that deal with clock before those that deal with mounting and fscking partitions helps?
Note that you must remove commands that symlink /etc/localtime in that case and cp /etc/localtime manually too.
Do not touch commands dealing with /var/lib/hwclock/adjtime though!
to live is to die
Offline
Done, error message is gone.
All your base are belong to us
Offline
Done, error message is gone.
Nice, so we will fix that bug soon.
to live is to die
Offline
Thanks a lot. Shouldn't this thread be marked as [solved]?
All your base are belong to us
Offline
Thanks a lot. Shouldn't this thread be marked as [solved]?
That can be done by original poster (skottish).
to live is to die
Offline