Bug 738435
Summary: | "Failed to refresh" error when attempting exclusive snap deletion from cluster VG on non active node | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Corey Marthaler <cmarthal> |
Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> |
lvm2 sub component: | Clustering / clvmd | QA Contact: | cluster-qe <cluster-qe> |
Status: | CLOSED WONTFIX | Docs Contact: | |
Severity: | medium | ||
Priority: | low | CC: | agk, dwysocha, heinzm, jbrassow, msnitzer, prajnoha, thornber, zkabelac |
Version: | 7.0 | Keywords: | Triaged |
Target Milestone: | pre-dev-freeze | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-18 18:07:56 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: | 756082 |
Description
Corey Marthaler
2011-09-14 19:05:13 UTC
One addition: clvmd after restart read initial lock state from "lvs" command. For virtual origin snapshot it loads wrong lock id (because virtual origin is internally represented by different LV). This must be fixed as well to make it work reliably. We should attempt to clean up the way it handles these sorts of situations. (We probably can't support deleting a snapshot from a node different from the one where it's active, though.) (We should perhaps consider this alongside the similar thin pool/volume activation questions.) 1. Maybe it's time to change the way locking is handled with volumes activated implicitly. Always hold locks for every active volume and have the code know how to acquire the extra locks? 2. See whether this lvremove sequence can be made to work correctly in a cluster - or if not, detect and ban it. This low priority and unlikely bug should continue to be tracked, but will not be considered for fix in RHEL6. Moving to RHEL7. Likely an attempt to reproduce there should be done. |