How to diagnose cluster fs resource failing to stop in RHEL 5 or 6

Solution Unverified - Updated -

Issue

  • Stopping cluster packages causes node reboot
  • When I stop a cluster service with an <fs> resource, it fails to unmount and reboots because self_fence is enabled
Sep 18 01:25:38 node1 clurgmgrd: [14718]: <err> 'umount /data/' failed, error=0 
Sep 18 01:25:38 node1 clurgmgrd: [14718]: <alert> umount failed - REBOOTING 
Sep 18 01:25:38 node1 kernel: md: stopping all md devices.
Sep 18 01:28:14 node1 syslogd 1.4.1: restart (remote reception).
  • How can I diagnose what is preventing my cluster fs resource from unmounting on stop?

Environment

  • Red Hat Enterprise Linux (RHEL) 5 or 6 with the High Availability Add On
  • rgmanager
  • One or more <fs> resources that fails to unmount properly when the service is stopping

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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