[CentOS] Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
Gabriele Pohl
gp at dipohl.deSun Jul 31 13:17:19 UTC 2016
- Previous message: [CentOS] Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
- Next message: [CentOS] LSI SATA MegaRaid & Centos 7 build 1511
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 27 Jul 2016 09:46:02 +0100 (BST) John Hodrien <J.H.Hodrien at leeds.ac.uk> wrote: > On Tue, 26 Jul 2016, Gabriele Pohl wrote: > > 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. > > 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 :) Cheers, Gabriele
- Previous message: [CentOS] Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
- Next message: [CentOS] LSI SATA MegaRaid & Centos 7 build 1511
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list