Why was the cluster node fenced when the following was logged: "controld(dlm)[13452]: ERROR: Uncontrolled lockspace exists, system must reboot. Executing suicide fencing"
Issue
A cluster node was rebooted after the following message was logged:
Nov 23 22:36:33 node42 controld(dlm)[13452]: ERROR: Uncontrolled lockspace exists, system must reboot. Executing suicide fencing
Environment
- Red Hat Enterprise Linux Server 7 (with the High Availability Add On)
pacemaker
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
