kworker/##:###+glock_workqueue threads become blocked in 'D' state during "do_xmote"
Issue
- Severs running gfs2 filesystems become hung or experience performance issues due to a large build up of
kworker/##:###+glock_workqueue
threads in a blocked ( D ) state. - In some cases these performance issues can result in a fencing event for the affected node due to reduced performance causing
Corosync
communication issues.
Environment
- Red Hat Enterprise Linux Server 8, 9 (with the High Availability Add On and Resilient Storage Add Ons)
- Pacemaker
- A Global Filesystem 2 (gfs2)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.