Bug 252241
| Summary: | self_fence missing from clusterfs.sh, preventing reboot if unmount fails | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Cluster Suite | Reporter: | Corey Marthaler <cmarthal> | ||||
| Component: | rgmanager | Assignee: | Lon Hohberger <lhh> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4 | CC: | cluster-maint, rkenna, rmccabe | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | RHBA-2007-1000 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-11-21 21:53:17 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 295781 | ||||||
| Attachments: |
|
||||||
|
Description
Corey Marthaler
2007-08-14 21:01:24 UTC
Here's the resource section of the .conf file:
<rm>
<failoverdomains>
<failoverdomain name="LINK_128_domain" ordered="0" restricted="0">
<failoverdomainnode name="link-02" priority="1"/>
<failoverdomainnode name="link-07" priority="1"/>
<failoverdomainnode name="link-08" priority="1"/>
</failoverdomain>
</failoverdomains>
<resources>
<ip address="10.15.89.209" monitor_link="1"/>
<clusterfs device="/dev/LINK_128/LINK_1280" force_unmount="1"
self_fence="1" fsid="3151" fstype="gfs" mountp
oint="/mnt/link0" name="LINK_1280" options=""/>
<fs device="/dev/LINK_128/LINK_1281" force_fsck="0" force_unmount="1"
self_fence="1" fsid="9968" fstype="ext
3" mountpoint="/mnt/link1" name="LINK_1281" options=""/>
<nfsexport name="LINK_128 nfs exports"/>
<nfsclient name="*" options="rw" target="*"/>
</resources>
<service autostart="1" domain="LINK_128_domain" name="nfs1" nfslock="1">
<clusterfs ref="LINK_1280">
<nfsexport ref="LINK_128 nfs exports">
<nfsclient ref="*"/>
</nfsexport>
</clusterfs>
<fs ref="LINK_1281">
<nfsexport ref="LINK_128 nfs exports">
<nfsclient ref="*"/>
</nfsexport>
</fs>
<ip ref="10.15.89.209"/>
</service>
</rm>
There are really two issues here: (1) A leaked lock or some other kind of reference prevented the unmount from succeeding. It's not likely an NFS lock, as even stopping nfsd/lockd wasn't able to clean it up. Fuser and lsof show no open refs on the file system, but nothing can unmount it. (2) rgmanager did NOT reboot the node even though unmount failed while self_fence was specified. As it turns out, clusterfs.sh does not support the self_fence option (only fs.sh - the non-cluster one). It's easy to add self_fence to clusterfs.sh. I'm going to create a clone bug for the lock leak. This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP. Created attachment 198851 [details]
Fixes behavior
Enables self_fence to work in clusterfs.sh resource agents.
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. http://rhn.redhat.com/errata/RHBA-2007-1000.html |