RHEL 5, 6, or 7 host reboots on its own when all storage paths fail and 'kernel.hung_task_panic = 1'
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_panicwhen storage devices become inaccessible?
Environment
- Red Hat Enterprise Linux (RHEL) 5, 6, or 7
kernel.hung_task_panic = 1in/etc/sysctl.conf, or/proc/sys/kernel/hung_task_paniccontains the value1- Utilizing
device-mapper-multipathfor managing redundant storage paths- Device is configured to queue I/O through
no_path_retryand/orqueue_if_no_path
- Device is configured to queue I/O through
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.