Gabriele Pohl
2016-Jul-26 16:38 UTC
[CentOS] Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
On Tue, 26 Jul 2016 16:21:00 +0100 (BST) John Hodrien <J.H.Hodrien at leeds.ac.uk> wrote:> On Tue, 26 Jul 2016, Gabriele Pohl wrote: > > > on all of my CentOS7 VMs on different hypervisors > > the config file e2fsck.conf contains the line > > > > broken_system_clock = 1 > > > > 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. > > 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 > $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, Gabriele
John Hodrien
2016-Jul-27 08:46 UTC
[CentOS] Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
On Tue, 26 Jul 2016, Gabriele Pohl wrote:> 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. jh
Gabriele Pohl
2016-Jul-31 13:17 UTC
[CentOS] Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
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
Possibly Parallel Threads
- Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
- Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
- Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
- Does e2fsck.conf contain "broken_system_clock = 1" per default on CentOS7?
- Recover from an fsck failure