My Favorites

Close

Please to see your favorites.


umount of NFS exported Filesystem fails in cluster during stop (PACEMAKER COROSYNC)

This document (7014619) is provided subject to the disclaimer at the end of this document.

Environment


SUSE Linux Enterprise High Availability Extension 11 Service Pack 2
SUSE Linux Enterprise High Availability Extension 11 Service Pack 3

Situation

In a setup where there is a resource stack build similar to

   ocf:heartbeat:Filesystem
   ocf:heartbeat:exportfs

under some circumstances there is the possibility that while the exportfs resource
is stopped the umount of the Filesystem will fail with "Device or Resource busy".

This failed stop will trigger a node fence in any supported enviroment.

Resolution

In this case it is possible to set the resource parameter

unlock_on_stop to 1

for example like

primitive test ocf:heartbeat:exportfs \
meta target-role="Stopped" \
operations $id="test-operations" \
op monitor interval="10" timeout="20" \
params clientspec="192.168.0.0/255.255.255.0" directory="/srv/nfs" fsid="666" unlock_on_stop="1"

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7014619
  • Creation Date:25-FEB-14
  • Modified Date:25-FEB-14
    • SUSESUSE Linux Enterprise High Availability Extension

Did this document solve your problem? Provide Feedback