fsck has gone 254 days without being checked
 

HI,

I am getting fsck message filesystem at boot time that has gone 254 days without being checked, check forced; for ext4 filesystem but in tune4fs -l <fs> its showing 6 months ?

Environment :- RHEL 5.7
Kernel :- 2.6.18-348.1.1.el5
Arch :- 64 bit

"it's showing 6 months" isn't particularly helpful, which section of the output is showing "it" as 6 months?

Actually in tune4fs -l <fs>, "Check interval" shows 6 months where the boot messages on the screen shows "has gone 254 days without being checked, check forced" after clearing the orphan inodes as the system was rebooted for fsck

my question is why there is a mismatch in fsck "check interval" ?

When was the server last rebooted?

The "check interval" is how long to go between checks, it's not the actual interval since the last check.

I hope, you have not understood my question as I mean,

check interval in tune4fs is showing 6 months where boot messages shows 254 days for fsck ?

And I hope you haven't misunderstood my question when I asked when was the server last rebooted?

Yes, so you keep saying, which to me, means that your server hadn't been rebooted for 254 days, so when it WAS rebooted it was over 6 months so fsck ran.

The server was manually rebooted 16 days back & fsck ran sucessfully but why there's a mismatch in fsck execution interval ?

Also, how can I check whether my filesystem check interval has been modified ?