Superblock last write time in in Future?

[buchalkalan]

Each time I boot my laptop, I come across this message during the booting process. It says

/12: superblock last write time is in the future. FIXED.
/12: clean 150332/1490944 files. 1105693/2955960 blocks
/home: recovering journal
/home: clean ---/---- files. ----/---- blocks
/boot1:recovering journal
/boot1: clean.......


/12 is the label for root file system (/). /home is for /home partition and /boot1 for /boot.

Can somebody enlighten me about this?

What is going on here?

[bob]

I'm no expert, but I believe this is a time sync problem. Have you noticed that your clock isn't always set to local time in Fedora? On some occasions, I've found it's set to GMT instead of my local time and if I've shut down and restarted, the computer's seeing times that haven't yet existed according to GMT. Yep, that explanation proves I'm no expert. Someone else with a correct answer, please bail me out....

[glennzo]

I may be out of my mind too but how about posting your /etc/fstab so we can have a look? If I'm way off too then maybe Bob and I will have to go sit in a corner together for a while.

[bob]

Watch your hands!!!!!

[buchalkalan]

bob - bail granted


my fstab

LABEL=/12               /                       ext3    defaults        1 1
LABEL=/home             /home                   ext3    defaults        1 2
LABEL=/boot1            /boot                   ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
LABEL=SWAP-sda8         swap                    swap    defaults        0 0
/dev/sda1       /home/malik/windows/C           ntfs-3g rw,defaults,umask=0000  0 0
/dev/sda5       /home/malik/windows/D           ntfs-3g rw,defaults,umask=0000  0 0
/dev/sda6       /home/malik/windows/E           ntfs-3g rw,defaults,umask=0000  0 0
/dev/sda7       /home/malik/windows/F           ntfs-3g rw,defaults,umask=0000  0 0

[glennzo]

Originally Posted by buchalkalan

bob - bail granted


my fstab

LABEL=/12               /                       ext3    defaults        1 1
LABEL=/home             /home                   ext3    defaults        1 2
LABEL=/boot1            /boot                   ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
LABEL=SWAP-sda8         swap                    swap    defaults        0 0
/dev/sda1       /home/malik/windows/C           ntfs-3g rw,defaults,umask=0000  0 0
/dev/sda5       /home/malik/windows/D           ntfs-3g rw,defaults,umask=0000  0 0
/dev/sda6       /home/malik/windows/E           ntfs-3g rw,defaults,umask=0000  0 0
/dev/sda7       /home/malik/windows/F           ntfs-3g rw,defaults,umask=0000  0 0

Just as I suspected. What I do, and it would probably be considered a hack by some, is change these lines,
LABEL=/12 / ext3 defaults 1 1
LABEL=/home /home ext3 defaults 1 2
LABEL=/boot1 /boot ext3 defaults 1 2
by getting rid of the 1 1, 1 2 at the end of the lines. Change them to 0 0 and the disk checking at boot will stop. They will then look like this:
LABEL=/12 / ext3 defaults 0 0
LABEL=/home /home ext3 defaults 0 0
LABEL=/boot1 /boot ext3 defaults 0 0

[glennzo]

Originally Posted by bob

Watch your hands!!!!!

That wasn't my hand

[buchalkalan]

modified accordingly, lemme check by a reboot.

[lmo]

You don't have system clock set to use UTC do you? I don't and I don't get that problem.

Just thinking out loud ...

[buchalkalan]

Originally Posted by glennzo

Just as I suspected. What I do, and it would probably be considered a hack by some, is change these lines,
LABEL=/12 / ext3 defaults 1 1
LABEL=/home /home ext3 defaults 1 2
LABEL=/boot1 /boot ext3 defaults 1 2
by getting rid of the 1 1, 1 2 at the end of the lines. Change them to 0 0 and the disk checking at boot will stop. They will then look like this:
LABEL=/12 / ext3 defaults 0 0
LABEL=/home /home ext3 defaults 0 0
LABEL=/boot1 /boot ext3 defaults 0 0

thanx.... works like a charm...

[glennzo]

You're welcome. I knew it would work. I just don't know how necessary it is to have that disk checking enabled. Disabling it has never been a problem for me, as far as I know, but someone else may know a little more that I do about it.

[buchalkalan]

Originally Posted by lmo

You don't have system clock set to use UTC do you? I don't and I don't get that problem.

Just thinking out loud ...

No, lmo, that's not the prob. I always exclude the UTC option as I am also running windows vista. Furthermore, there r some known issues with the current kernel 2.6, and it doesn't allow u to play with time if u haven't used noapic option during the boot. At least this is the case for me, without noapic option, when i try to do anything with the clock applet my system hangs and nothing works except a manual reboot.

[lmo]

Really what caused that message is that, for some reason, the hardware clock did not get set up [correctly] before the fsck test. By setting 0 0, the integrity check (to see if fsck ought to be run) won't get done as the designers had planned. I think these are somewhere in rc.sysinit. I also saw it do something with clock at shutdown in /etc/rc.d/rc0.d/S01halt.

And somebody said ... Shutdown hangs at clocksync.