Are you stopping the NFS server before trying to unmount? If the resource is busy heartbeat will not be able to unmount it.
Rajkumar Agrawal wrote: > Hi, > We installed the NFS-ha for the high availability of NFS server. For the > testing, when we stop the heartbeat service at primary node, primary > node is not releasing the resource for the secondary. We get this from > ha-log. So secondary node is not able to take over the resource. The > /var/log/ha-log of primary node are : > > Filesystem[7192]: 2009/12/04_16:22:20 ERROR: Couldn't unmount > /dvshare; trying cleanup with SIGKILL > Filesystem[7192]: 2009/12/04_16:22:20 INFO: No processes on > /dvshare were signalled > Filesystem[7192]: 2009/12/04_16:22:21 ERROR: Couldn't unmount > /dvshare, giving up! > Filesystem[7181]: 2009/12/04_16:22:21 ERROR: Generic error > ResourceManager[5157]: 2009/12/04_16:22:21 ERROR: Return code 1 from > /etc/ha.d/resource.d/Filesystem > Filesystem[7353]: 2009/12/04_16:22:21 INFO: Running OK > ResourceManager[5157]: 2009/12/04_16:22:21 CRIT: Resource STOP failure. > Reboot required! > ResourceManager[5157]: 2009/12/04_16:22:21 CRIT: Killing heartbeat > ungracefully! > > > Plz help us to troubleshoot this. > > Thanks > Rajkumar Agrawal > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
