Bug 1020877
| Summary: | lvm2 does mishandle implicit availability changes | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Zdenek Kabelac <zkabelac> |
| Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> |
| lvm2 sub component: | Clustering / clvmd (RHEL6) | QA Contact: | Cluster QE <mspqa-list> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | agk, dwysocha, heinzm, jbrassow, lvm-team, msnitzer, nperic, prajnoha, prockai, thornber, zkabelac |
| Version: | 6.6 | Flags: | nperic:
needinfo-
|
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.107-1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
In the cluster many volume types support only exclusive activation (snapshot, thins...). lmv2 tool has been automatically converting then any non-exclusive activation into 'exclusive' activation.
Consequence:
Such conversion however is not always correct. When a user has requested local activation, volume could have been activated exclusively on a different node in cluster.
Fix:
Local activation is properly converted into local-exclusive activation.
Result:
When the local activation is successful the volume is locally and exclusively active.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-14 08:24:50 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
Zdenek Kabelac
2013-10-18 12:23:14 UTC
This has been improved with upstream patch: https://www.redhat.com/archives/lvm-devel/2013-November/msg00002.html Tested activation and deactivation of raid1, thin pools, ordinary LVs and snapshots of ordinary LVs and thin LVs. There was a small issue with LVM behavior if an already inactive LV was being told to deactivate, which I opened a separate bug for (Bug #1124766) Additional issues with commands which are handling activation/deactivation are: -aen == -an which may not be what a user wants (it deactivates the LV on ALL the nodes, regardless of the fact that there may be no exclusively activated LVs) -aly fails silently, and returns 0 (even though id doesn't do anything) in case the volume_list check does not pass: [root@virt-064 ~]# grep " volume_list" /etc/lvm/lvm.conf volume_list = [ "vg1", "@tag1", "cluster/linear" ] [root@virt-064 ~]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert linear cluster -wi------- 1.00g lvol1 cluster Vwi---tz-k 10.00g pool thin_lv pool cluster twi---tz-- 2.00g 0.00 1.17 raid1 cluster rwi---r--- 2.00g thin_lv cluster Vwi-a-tz-- 10.00g pool 0.00 lv_root vg_virt064 -wi-ao---- 6.71g lv_swap vg_virt064 -wi-ao---- 816.00m [root@virt-064 ~]# lvchange -aly cluster/raid1 [root@virt-064 ~]# echo $? 0 [root@virt-064 ~]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert linear cluster -wi------- 1.00g lvol1 cluster Vwi---tz-k 10.00g pool thin_lv pool cluster twi---tz-- 2.00g 0.00 1.17 raid1 cluster rwi---r--- 2.00g thin_lv cluster Vwi-a-tz-- 10.00g pool 0.00 lv_root vg_virt064 -wi-ao---- 6.71g lv_swap vg_virt064 -wi-ao---- 816.00m [root@virt-064 ~]# It should try and at least warn the user that it didn't actually DO anything. Should this all be split into more bug reports or can it be handled inside this one which is related to handling the availability changes? Changing the needinfo to another address. Closing this bug as VERIFIED since the intended behaviour can be observed. However, will open a new bug for the funny things with CLI arguments. Marking it verified with: lvm2-2.02.109-1.el6 BUILT: Tue Aug 5 17:36:23 CEST 2014 lvm2-libs-2.02.109-1.el6 BUILT: Tue Aug 5 17:36:23 CEST 2014 lvm2-cluster-2.02.109-1.el6 BUILT: Tue Aug 5 17:36:23 CEST 2014 udev-147-2.57.el6 BUILT: Thu Jul 24 15:48:47 CEST 2014 device-mapper-1.02.88-1.el6 BUILT: Tue Aug 5 17:36:23 CEST 2014 device-mapper-libs-1.02.88-1.el6 BUILT: Tue Aug 5 17:36:23 CEST 2014 device-mapper-event-1.02.88-1.el6 BUILT: Tue Aug 5 17:36:23 CEST 2014 device-mapper-event-libs-1.02.88-1.el6 BUILT: Tue Aug 5 17:36:23 CEST 2014 device-mapper-persistent-data-0.3.2-1.el6 BUILT: Fri Apr 4 15:43:06 CEST 2014 cmirror-2.02.109-1.el6 BUILT: Tue Aug 5 17:36:23 CEST 2014 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. http://rhn.redhat.com/errata/RHBA-2014-1387.html |