Server panics with "kernel BUG at fs/gfs2/glock.c:670! " message

Solution Verified - Updated -

Issue

A cluster node panics with the kernel BUG at fs/gfs2/glock.c:670! panic message:

$ cat vmcore-dmesg.txt
--------------------------------------->8--------------------------------------
[610956.706353] kernel BUG at fs/gfs2/glock.c:670! <<=====
[610956.706499] invalid opcode: 0000 [#1] SMP NOPTI
[610956.706633] CPU: 15 PID: 3271961 Comm: kworker/15:0H Kdump: loaded Tainted: G        W  OE    --------- -  - 4.18.0-477.10.1.el8_8.x86_64 #1
[610956.706896] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 07/14/2022
[610956.707034] Workqueue: glock_workqueue glock_work_func [gfs2]
[610956.707165] RIP: 0010:do_xmote+0x29e/0x340 [gfs2] <<=====
--------------------------------------->8--------------------------------------
[610956.709104] Call Trace:
[610956.709232]  finish_xmote+0x263/0x320 [gfs2] <<=====
[610956.709369]  glock_work_func+0xd6/0x110 [gfs2] <<=====
[610956.709507]  process_one_work+0x1a7/0x360
[610956.709644]  ? create_worker+0x1a0/0x1a0
[610956.709778]  worker_thread+0x30/0x390
[610956.709911]  ? create_worker+0x1a0/0x1a0
[610956.710045]  kthread+0x134/0x150
[610956.710180]  ? set_kthread_struct+0x50/0x50
[610956.710316]  ret_from_fork+0x1f/0x40

Environment

  • Red Hat Enterprise Linux Server 8, 9 (with the Resilient Storage Add-On)
  • A Global Filesystem 2 (gfs2)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content