Bug 449110
Summary: | cmirror down conversion after failure is broken | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Corey Marthaler <cmarthal> |
Component: | cmirror-kernel | Assignee: | Jonathan Earl Brassow <jbrassow> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 4 | CC: | agk, cfeist, dwysocha, edamato, jbrassow, mbroz, prockai |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-07-24 16:31:14 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: |
Description
Corey Marthaler
2008-05-30 14:00:54 UTC
Single machine mirror device failures work just fine. What if you kill dmeventd and run 'vgreduce --removemissing <vg>' by hand? That would tell us if the problem is in dmeventd. first try ok. second time ok... I think you may be omitting some information on how to reproduce? Try testing with increased timeout for clvmd.... Seems to work for me. I set the command timeout to 600 (instead of 90) trying to reduce logging in cmirror module to reduce response time... perhaps bringing it under the clvmd timeout. It appears that this bug has mysterious been fixed with the latest rpms: device-mapper-1.02.25-2.el4 lvm2-cluster-2.02.37-2.el4 lvm2-2.02.37-2.el4 The clvmd locking timeout made no difference when I downgraded. I reproduced this everytime regardless. Also, when I upgraded, I could no longer reproduce this, even with the locking time out set to the default. Marking this verified. Closing this bug as it has been released in 4.7. |