Does E2fsck.conf Contain “broken_system_clock = 1” Per Default On CentOS7?

Home » CentOS » Does E2fsck.conf Contain “broken_system_clock = 1” Per Default On CentOS7?
CentOS 6 Comments


on all of my CentOS7 VMs on different hypervisors the config file e2fsck.conf contains the line

broken_system_clock = 1

I found this because on all of them, the root partition was not checked triggered by interval setting with tune2fs.

Do you see similiar /default/ settings on your machines? Is it an issue only on VMs?
I have no CentOS7 host on bare metal to compare.

Thanks and cheers,


6 thoughts on - Does E2fsck.conf Contain “broken_system_clock = 1” Per Default On CentOS7?

  • Same on real hardware. But you can check this yourself:

    $ rpm -qf /etc/e2fsck.conf e2fsprogs-1.42.9-7.el7.x86_64
    $ rpm -V e2fsprogs
    $ rpm -q e2fsprogs –scripts

    So it’s a file provided by e2fsprogs, it’s not been changed since you installed it, and there’s no script in the package.


  • thanks for the hint :)

    I now changed the value to 0 and rebooted.

    After that fsck based on Interval setting were done.

    Unfortunately that is not true for the root partition. For that I had to use maxCount settings to trigger fsck.

    fyi and cheers,


  • I believe e2fsk happens both pre root mount, and post. You’ll want to rebuild your initramfs to make it take effect for the root volume I’d guess.


  • agreed as I see the config is included there:

    # lsinitrd | grep e2fsck
    -rw-r–r– 1 root root 112 Mar 5 2015 etc/e2fsck.conf
    -rwxr-xr-x 3 root root 0 Jun 25 06:56 usr/sbin/e2fsck

    I have to wait for the next maintenance downtime to verify.

    I will report the result then.

    Thanks again for your help :)