fs or clusterfs resource fails to stop when a process is using shared memory or libraries backed by the resource's mountpoint in a RHEL 6 High Availability cluster
Issue
- My fs resource fails to stop, even though I have
force_unmount
enabled - If a process has a shared library or shared memory segments on the mountpoint for a cluster-managed
fs
orclusterfs
resource,rgmanager
can't stop that resource and the node self-fences
Mar 08 18:21:04 rgmanager Stopping service service:myService
Mar 08 18:21:26 rgmanager [fs] unmounting /myFS
Mar 08 18:21:26 rgmanager [fs] umount failed: 1
Mar 08 18:21:26 rgmanager [fs] Sending SIGTERM to processes on /myFS
Mar 08 18:21:31 rgmanager [fs] unmounting /myFS
Mar 08 18:21:31 rgmanager [fs] umount failed: 1
Mar 08 18:21:31 rgmanager [fs] Sending SIGKILL to processes on /myFS
Mar 08 18:21:36 rgmanager [fs] unmounting /myFS
Mar 08 18:21:36 rgmanager [fs] umount failed: 1
Mar 08 18:21:37 rgmanager [fs] Sending SIGKILL to processes on /myFS
Mar 08 18:21:37 rgmanager [fs] 'umount /myFS' failed, error=1
Mar 08 18:21:37 rgmanager [fs] umount failed - REBOOTING
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
resource-agents
releases starting with3.9.2-40.el6
up to, but not including,3.9.5-12.el6
- One or more
<fs/>
,<clusterfs/>
, or<netfs/>
resources in a service in/etc/cluster/cluster.conf
- One or more processes that load a shared library or use shared memory that is stored on or backed by the mountpoint of one of those resources
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.