Home / server / Questions / 378846
Accepted
Zac B
Asked: 2012-04-13 05:39:20 +0800 CST

CentOS disable filesystem check: superblock last mount time is in the future

  • 772

I'm persistently getting the "Superblock last mount time is in the future" error when booting CentOS 6. I've seen other questions which ask how to resolve this error, but I know exactly why it's occurring: our development/testing VMs regularly have their date set to times far from the present, and have all of their filesystems remounted.

What I want to know is: how do I disable all consistency checking for superblock mount time in centOS?

I've tried tune2fs -i 0 <device> and setting buggy_init_scripts=1 in /etc/e2fsck.conf and neither has worked; the problem persists.

centos filesystems ext3 fsck centos6

3 Answers

  1. Best Answer

    buggy_init_scripts=1 only works if the time difference is smaller than 1 hour.

    Try that int /etc/e2fsck.conf:

    [problems] 

    # Superblock last mount time is in the future (PR_0_FUTURE_SB_LAST_MOUNT).
0x000031 = {
    preen_ok = true
    preen_nomessage = true
}

# Superblock last write time is in the future (PR_0_FUTURE_SB_LAST_WRITE).
0x000032 = {
    preen_ok = true
    preen_nomessage = true
}

    This should remove the message, and correct the datas.

    • 4

  2. It is better that you fix the vm datetime. It is quite a complicated issue actually if by vm you mean vmware.

    http://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf

    if it is some other vm system, i think the issue would be similar.

    turning off consistency check etc. is not advisable because they are there for a reason. a system with time being inconsistent will affect integrity in many other ways.

    • 3

  3. Build the hwclock time set into your kickstart/build process.

    • 2