cluster service with an fs resource fails to stop or relocate because samba-exporting service for that fs hasn't stopped yet in a RHEL 5 or 6 High Availability cluster

Solution In Progress - Updated -

Issue

  • My service containing an fs resource needed to failover, but couldn't stop
  • I have a service that starts samba exporting several file systems that are in other services so that they can be started and stopped independently. When one of the services went to fail over, it failed to stop seemingly because it was still in use. The samba service was able to stop after that just fine.
Mar  3 22:21:45 node1 rgmanager[61683]: [fs] unmounting /myFS
Mar  3 22:21:45 node1 rgmanager[61877]: [fs] Sending SIGTERM to processes on /myFS
Mar  3 22:21:51 node1 rgmanager[63052]: [fs] unmounting /myFS
Mar  3 22:21:51 node1 rgmanager[63157]: [fs] Sending SIGKILL to processes on /myFS
Mar  3 22:21:51 node1 rgmanager[4104]: stop on fs "myfilesystem" returned 1 (generic error)
Mar  3 22:21:51 node1 rgmanager[4104]: stop on lvm "my-halvm" returned 1 (generic error)
  Mar  3 22:21:51 node1 rgmanager[4104]: #12: RG service:myService failed to stop; intervention required
  Mar  3 22:21:51 node1 rgmanager[4104]: Service service:myService is failed
  [...]
  Mar  3 22:22:00 node1 rgmanager[4104]: Stopping service service:samba

Environment

  • Red Hat Enterprise Linux (RHEL) 5 or 6 with the High Availability Add On
  • rgmanager
  • One or more services in /etc/cluster/cluster.conf that contain an <fs> resource that is exported by a samba resource in a separate service

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content