Bug 1533932
Summary: | Locking error when merging thin snapshot | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Roman Bednář <rbednar> |
Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> |
lvm2 sub component: | Thin Provisioning | QA Contact: | cluster-qe <cluster-qe> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | CC: | agk, heinzm, jbrassow, mcsontos, msnitzer, prajnoha, prockai, rhandlin, thornber, zkabelac |
Version: | 7.5 | Keywords: | Regression |
Target Milestone: | rc | Flags: | rhandlin:
needinfo+
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | lvm2-2.02.177-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 15:23:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Roman Bednář
2018-01-12 15:01:27 UTC
The issue seems to popup as a race on cluster - where the reactivate origin needs to be activated exclusively. Reasonable simple fix: diff --git a/tools/lvconvert.c b/tools/lvconvert.c index deb7cc909..618d81953 100644 --- a/tools/lvconvert.c +++ b/tools/lvconvert.c @@ -2170,7 +2170,7 @@ static int _lvconvert_merge_thin_snapshot(struct cmd_context *cmd, log_print_unless_silent("Volume %s replaced origin %s.", display_lvname(origin), display_lvname(lv)); - if (origin_is_active && !activate_lv(cmd, lv)) { + if (origin_is_active && !activate_lv_excl(cmd, lv)) { log_error("Failed to reactivate origin %s.", display_lvname(lv)); return 0; Believed it's fixed upstream with these patch (fixing also few other possibly locking problems for lvconvert and stacking). https://www.redhat.com/archives/lvm-devel/2018-January/msg00049.html Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0853 |