Bug 1254393
Summary: | pvremove of a device under cloned vg fails | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Shivananda <Shivananda.KN> | ||||||||
Component: | lvm2 | Assignee: | David Teigland <teigland> | ||||||||
lvm2 sub component: | Scripts / lvmdump / vgimportclone | QA Contact: | cluster-qe <cluster-qe> | ||||||||
Status: | CLOSED ERRATA | Docs Contact: | |||||||||
Severity: | high | ||||||||||
Priority: | unspecified | CC: | agk, ayyanar, ayyanar.perumal, girishkh, gowrav.mahadevaiah, heinzm, hkathed, jbrassow, lmiksik, marting, mcsontos, msnitzer, prajnoha, prockai, rbednar, Shivananda.KN, sudharss, vanishri.n, vprabhu, xdl-redhat-bugzilla, zkabelac | ||||||||
Version: | 7.1 | ||||||||||
Target Milestone: | rc | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | lvm2-2.02.161-1.el7 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2016-11-04 04:10:22 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: | |||||||||||
Attachments: |
|
Description
Shivananda
2015-08-18 00:46:38 UTC
Hello, could you please upload a journal/messages from the affected system? I am surprised pvscan and vgscan had not complained about seeing duplicate UUIDs. I understand the tstvg/tstlvol was active while rescanning the SCSI bus and it looks like the tstvg's PV /dev/mapper/3600a098054313968772b334e2f627648 was somehow silently replaced by the new block device /dev/mapper/3600a098054313968772b334e2f627649. > 3. Create a clone of the LUN from the hardware snapshot Was the original LUN unmapped here? > 4. Map the cloned LUN to the host and discover it What do `dmsetup status` and `multipath -ll` say before and after rescanning SCSI bus? Created attachment 1064935 [details]
Console o/p captured while cloning
Created attachment 1064936 [details]
dmesg o/p during cloning operation
> could you please upload a journal/messages from the affected system? Attached the console as well as dmesg o/p in another attempt to reproduce this. Let me know if that is not sufficient and any specific logs/messages you wish to have. > Was the original LUN unmapped here? No, the original LUN was mapped and VG/LV were active > What do `dmsetup status` and `multipath -ll` say before and after rescanning SCSI bus? Refer the attached console o/p in another attempt to reproduce this. When hit the pvremove failure, please, try to collect the output of following commands: lsof lsblk lvmdump -l -s (mainly to collect relevant lvmetad and systemd unit info) Is this reproducible if you set use_lvmetad=0 in lvm.conf? Created attachment 1087249 [details]
lsof, lsblk and lvmdump -l -s command output
It's not reproducible if use_lvmetad=0 in lvm.conf More duplicate PV signature issues... Dave, could you take a look? If multipath is not configured and host sees only one path we do not have a workaround (worked around by issuing 'multipath -F' and 'multipath -r). The only alternative we see now is to stop lvm2-lvmetad.service or set use_lvmetad=0 in lvm.conf. Let us know if there is any other workaround that we can implement to overcome the issue. Handling of duplicate pvs will be much improved in 7.3 and these issues will probably be solved. (lvmetad will be automatically disabled while duplicates exist.) Thanks, David for the update that 'lvmetad' will be automatically disabled. However, I assume that 'lvmetad' will be enabled by 'vgimportlcone' after resolving duplicate PVs. Adding QA ack for 7.3. Marking verified with latest rpms. LVM does not use lvmetad data from now on when duplicate PV is detected until solved. Then it automatically restores normal operation. # pvs -o +uuid WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Use multipath or vgimportclone to resolve duplicate PVs? WARNING: After duplicates are resolved, run "pvscan --cache" to enable lvmetad. WARNING: PV mGsQGs-y0Xr-xAEB-aKzU-CLKw-fpHy-RN64tu on /dev/sdj was already found on /dev/sdi. WARNING: PV mGsQGs-y0Xr-xAEB-aKzU-CLKw-fpHy-RN64tu prefers device /dev/sdi because device was seen first. PV VG Fmt Attr PSize PFree PV UUID /dev/sdi cloneofvg lvm2 a-- 972.00m 972.00m mGsQGs-y0Xr-xAEB-aKzU-CLKw-fpHy-RN64tu /dev/vda2 rhel_virt-283 lvm2 a-- 7.79g 40.00m RgLVtC-zhsS-aSpi-Qf8F-HcKk-LzhJ-ViCb8D # systemctl is-active lvm2-lvmetad active 3.10.0-505.el7.x86_64 lvm2-2.02.165-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016 lvm2-libs-2.02.165-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016 lvm2-cluster-2.02.165-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016 device-mapper-1.02.134-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016 device-mapper-libs-1.02.134-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016 device-mapper-event-1.02.134-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016 device-mapper-event-libs-1.02.134-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016 device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 12:29:13 CEST 2016 cmirror-2.02.165-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016 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://rhn.redhat.com/errata/RHBA-2016-1445.html |