Red Hat Bugzilla – Bug 440645
service failover hangs at quotaoff in /usr/share/cluster/fs.sh
Last modified: 2010-10-22 19:45:59 EDT
Description of problem:
Under certain circumstances the quotaoff command may hang while disabling quotas
for an NFS mounted volume (for e.g. if the server or rpc.quotad is unavailable).
This causes the /usr/share/cluster/fs.sh agent to hang shutting down the resource.
Quotaoff should not hang but if quotas are not enabled or wanted for the file
system concerned it's better to avoid the problem by just not running it.
Version-Release number of selected component (if applicable):
100% for certain configurations
Steps to Reproduce:
1. Configure a file system resource that mounts an NFS server
2. Activate the resource on a node
3. Make the NFS server go away
4. Try to shutdown or relocate the service
fs.sh hangs at quotaoff
fs.sh does not hang & shutdown / relocation completes with success
This was originally seen in a case where nodes were mounting their own NFS
exports. When the service was shut down, the NFS server stopped first causing
the quotaoff to hang. After discussion with Lon he provided a patch (attached)
to work around this by avoiding running quotaoff if quotas are not configured
for a given file system.
Created attachment 300415 [details]
Patch to avoid running quotaoff for file systems with no quotas configured
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Pushed to RHEL4 git branch
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.