Bug 1685723
| Summary: | exclusive native vdo with lvmlockd will leave remnant lock and cause vgchange to fail "VG stop failed: LVs must first be deactivated" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | David Teigland <teigland> |
| lvm2 sub component: | LVM lock daemon / lvmlockd | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | high | CC: | agk, heinzm, jbrassow, mcsontos, pasik, prajnoha, teigland, zkabelac |
| Version: | 8.0 | ||
| Target Milestone: | rc | ||
| Target Release: | 8.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.03.11-0.2.20201103git8801a86.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-18 15:01:41 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
Corey Marthaler
2019-03-05 22:07:02 UTC
pushed to master https://sourceware.org/git/?p=lvm2.git;a=commit;h=2272a32e6f9b99f98514e58de82f8a3baa8b46da $ lvcreate --type vdo -L5G -n vv test WARNING: vdo signature detected on /dev/test/vpool0 at offset 0. Wipe it? [y/n]: y Wiping vdo signature on /dev/test/vpool0. Logical blocks defaulted to 523108 blocks. The VDO volume can address 2 GB in 1 data slab. It can grow to address at most 16 TB of physical storage in 8192 slabs. If a larger maximum size might be needed, use bigger slabs. Logical volume "vv" created. $ lvs -o+uuid test LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert LV UUID vpool0 test dwi------- 5.00g 60.03 fhFoim-Lj9R-Gfbs-fwms-gfVQ-VFCo-ZS4RVr vv test vwi-a-v--- 1.99g vpool0 0.00 YdwVMl-dvia-wNyu-Nm2s-d9Ua-lcDe-Uzv81R $ dlm_tool lockdebug lvm_test Resource len 4 "VGLK" Master LVB len 32 seq 2 01 01 00 00 49 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Granted 00000001 NL Resource len 38 "fhFoim-Lj9R-Gfbs-fwms-gfVQ-VFCo-ZS4RVr" Master Granted 00000002 EX $ lvremove test/vv Do you really want to remove active logical volume test/vv? [y/n]: y Logical volume "vv" successfully removed $ dlm_tool lockdebug lvm_test Resource len 4 "VGLK" Master LVB len 32 seq 3 01 01 00 00 4a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Granted 00000001 NL Resource len 38 "fhFoim-Lj9R-Gfbs-fwms-gfVQ-VFCo-ZS4RVr" Master Dir $ vgchange --lockstop test $ dlm_tool ls $ lvmlockctl -i $ dmsetup ls rhel-swap (253:1) rhel-root (253:0) Fix verified in the latest rpms.
kernel-4.18.0-259.el8.dt4 BUILT: Sat Dec 12 14:40:07 CST 2020
lvm2-2.03.11-0.3.20201210git9fe7aba.el8 BUILT: Thu Dec 10 09:44:53 CST 2020
lvm2-libs-2.03.11-0.3.20201210git9fe7aba.el8 BUILT: Thu Dec 10 09:44:53 CST 2020
[root@host-087 ~]# vgs
VG #PV #LV #SN Attr VSize VFree
testvg 8 0 0 wz--ns <239.91g <239.91g
[root@host-087 ~]# lvcreate --activate ey --yes --type vdo -n vdo1 -L 6G testvg
Logical blocks defaulted to 523108 blocks.
The VDO volume can address 2 GB in 1 data slab.
It can grow to address at most 16 TB of physical storage in 8192 slabs.
If a larger maximum size might be needed, use bigger slabs.
Logical volume "vdo1" created.
[root@host-087 ~]# lvs -a -o +devices
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert Devices
vdo1 testvg vwi-a-v--- 1.99g vpool0 0.00 vpool0(0)
vpool0 testvg dwi------- 6.00g 66.69 vpool0_vdata(0)
[vpool0_vdata] testvg Dwi-ao---- 6.00g /dev/sda1(0)
[root@host-087 ~]# lvchange -an testvg
[root@host-087 ~]# lvs -a -o +devices
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert Devices
vdo1 testvg vwi---v--- 1.99g vpool0 vpool0(0)
vpool0 testvg dwi------- 6.00g vpool0_vdata(0)
[vpool0_vdata] testvg Dwi------- 6.00g /dev/sda1(0)
[root@host-087 ~]# lvremove testvg
Removing VDO pool "vpool0" will remove 1 dependent volume(s). Proceed? [y/n]: y
Logical volume "vdo1" successfully removed
[root@host-087 ~]# dmsetup ls
[root@host-087 ~]# vgchange --lock-stop testvg
[root@host-087 ~]# dlm_tool ls
[root@host-087 ~]# lvmlockctl -i
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 (lvm2 bug fix and enhancement update), 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/RHBA-2021:1659 |