On 28/10/2023 08.58, Eyal Lebedinsky wrote:
Fully updated F28.
I had to send one (of 7) member disk for RMA.
I notice that the system is very non responsive. 'top' shows
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1365697 root 20 0 0 0 0 R 93.8 0.0 384:40.55 kworker/u16:3+flush-9:127
This continues even when there are no user actions (ff, tb closed).
A few days ago it stopped, but today I see that it kept running all night where there were
period of inactivity for a few hours.
As another point: a few days ago I received a disk from RMA and the recovery went as fast as expected.
I then removed another disk to send for RMA.
Is this expected? Is there anything I can do to improve the situation?
TIA
An observation that may be of value. I notice
$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : active raid6 sde1[4] sdg1[6] sdf1[5] sdd1[7] sdb1[8] sdc1[9]
58593761280 blocks super 1.2 level 6, 512k chunk, algorithm 2 [7/6] [_UUUUUU]
bitmap: 87/88 pages [348KB], 65536KB chunk
And I usually see the bitmap showing as 0/88 or 1/88, so does this indicate that some
housekeeping work is outstanding? Related to the very busy kworker?
--
Eyal at Home (fedora@xxxxxxxxxxxxxx)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
