Node does not reboot when "self_fence=on" and "force_unmount=on" are set and a submount causes an fs resource to fail in RHEL 6

Solution Verified - Updated -

Issue

  • If an fs (filesystem) resource fails to stop due to an active submount, self_fence is not honored (the node doesn't reboot).
  • The self_fence=on logic doesn't get triggered in some situations when force_unmount option is enabled.

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • resource-agents releases prior to 3.9.2-40.el6
  • One or more filesystem-based resources (fs, clusterfs, netfs, etc) in /etc/cluster/cluster.conf.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.