RHEL host reboots on its own when all storage paths fail and 'kernel.hung_task_panic = 1'

Solution Unverified - Updated -

Issue

  • We're doing storage failure testing and when we take down all paths on one host, that host reboots on its own
  • A cluster node is losing all paths to a GFS2 storage device and then it stops responding and gets fenced
  • Why does a host reboot with kernel.hung_task_panic when storage devices become inaccessible?

Environment

  • Red Hat Enterprise Linux (RHEL) 5, 6, 7, 8, 9
  • kernel.hung_task_panic = 1 in /etc/sysctl.conf, or /proc/sys/kernel/hung_task_panic contains the value 1
  • Utilizing device-mapper-multipath for managing redundant storage paths

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