I updated my backup server this weekend from CentOS 7 to CentOS 8. OS disk is SSD, /dev/md0 are two 4TB WD mechanical drives. No hardware was changed.
1. wiped all drives 2. installed new copy of 8 on system SSD 3. re-created the 4TB mirror /dev/md0 with the same WD mechanical drives 4. created the largest single partition possible on /dev/md0 and formatted it ext4 5. waited several hours for the creation of /dev/md0 to finish 6. copied all data back onto /dev/md0
Both installs were a full workstation, with Gnome. The mirror is mounted via fstab as: /dev/md0 /mnt/raid1 ext4 defaults 0 0
Under CentOS 7 the /dev/md0 mirror was silent when not in use. Now under 8, the hard drives are constantly "pinged" by some process, at about the same frequency as a heartbeat monitor. I can not figure out what process is keeping them active. iotop does show a process named [ext4lazyinput].
Is there something I've missed?
Hi,
Ext4 is (slowly) initializing group blocks as far as I can remember. Patience should do the trick :)
HTH,
Le 3 février 2020 20:28:27 GMT+01:00, Chris Pemberton pchris.bci@gmail.com a écrit :
I updated my backup server this weekend from CentOS 7 to CentOS 8. OS disk is SSD, /dev/md0 are two 4TB WD mechanical drives. No hardware was changed.
- wiped all drives
- installed new copy of 8 on system SSD
- re-created the 4TB mirror /dev/md0 with the same WD mechanical
drives 4. created the largest single partition possible on /dev/md0 and formatted it ext4 5. waited several hours for the creation of /dev/md0 to finish 6. copied all data back onto /dev/md0
Both installs were a full workstation, with Gnome. The mirror is mounted via fstab as: /dev/md0 /mnt/raid1 ext4 defaults 0 0
Under CentOS 7 the /dev/md0 mirror was silent when not in use. Now under 8, the hard drives are constantly "pinged" by some process, at about the same frequency as a heartbeat monitor. I can not figure out what process is keeping them active. iotop does show a process named [ext4lazyinput].
Is there something I've missed? _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 2/3/20 3:13 PM, Laurent Wandrebeck wrote:
Hi,
Ext4 is (slowly) initializing group blocks as far as I can remember. Patience should do the trick :)
Indeed. See the manpage for mkfs.ext4 and scroll down to the "lazy_itable_init" extended option, which is enabled by default.
Be patient...
You are likely correct as the [ext4lazyinput] process is now gone. Probably finished up last night as the drives are quiet now.
For completeness:
What did "cat /proc/mdstat" say?
# cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdc1[1] sdb1[0] 3906885440 blocks super 1.2 [2/2] [UU] bitmap: 0/30 pages [0KB], 65536KB chunk
unused devices: <none>
Unfortunely, I can not be 100% certain if the [ext4lazyinput] process was still active when I captured the mdstat output shown above. But that is what it says now that the process is gone.
Thanks to everyone for their input.