Skip to navigation

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

Updated 2014-03-12T15:48:13+00:00

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 content preview. For full access to the Red Hat Knowledgebase, please log in.

Not a subscriber? Learn more about the benefits of Red Hat Subscriptions.