Bug 2168703
| Summary: | vgimportclone.c "Using new VG name" doesn't actually check if name is new and can hang if it's not | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | David Teigland <teigland> |
| lvm2 sub component: | Scripts / lvmdump / vgimportclone | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | low | ||
| Priority: | unspecified | CC: | agk, heinzm, jbrassow, mcsontos, msnitzer, prajnoha, teigland, zkabelac |
| Version: | 9.2 | Keywords: | Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.03.21-1.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-11-07 08:53:33 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
2023-02-09 19:26:56 UTC
fix in main: https://sourceware.org/git/?p=lvm2.git;a=commit;h=be124ae81027e8736106e4958bd2dfab971d6764 $ pvs PV VG Fmt Attr PSize PFree /dev/loop0 foo lvm2 a-- 4.00m 4.00m $ vgimportclone -n foo /dev/loop0 $ pvs PV VG Fmt Attr PSize PFree /dev/loop0 foo1 lvm2 a-- 4.00m 4.00m $ pvs PV VG Fmt Attr PSize PFree /dev/loop0 foo lvm2 a-- 4.00m 4.00m /dev/loop1 foo1 lvm2 a-- 4.00m 4.00m $ vgimportclone -n foo /dev/loop0 $ pvs PV VG Fmt Attr PSize PFree /dev/loop0 foo2 lvm2 a-- 4.00m 4.00m /dev/loop1 foo1 lvm2 a-- 4.00m 4.00m Marking Verfied:Tested in the latest rpms. kernel-5.14.0-306.el9 BUILT: Sat Apr 29 05:45:15 PM CEST 2023 lvm2-2.03.21-1.el9 BUILT: Fri Apr 21 02:33:33 PM CEST 2023 lvm2-libs-2.03.21-1.el9 BUILT: Fri Apr 21 02:33:33 PM CEST 2023 [root@grant-01 ~]# pvscan PV /dev/sdb1 VG foo lvm2 [<447.13 GiB / <447.13 GiB free] PV /dev/sdc1 VG foo lvm2 [<447.13 GiB / <447.13 GiB free] PV /dev/sdd1 VG foo lvm2 [<447.13 GiB / <447.13 GiB free] Total: 3 [<1.31 TiB] / in use: 3 [<1.31 TiB] / in no VG: 0 [0 ] [root@grant-01 ~]# vgimportclone -n foo /dev/sdb1 /dev/sdc1 /dev/sdd1 [root@grant-01 ~]# pvscan PV /dev/sdb1 VG foo1 lvm2 [<447.13 GiB / <447.13 GiB free] PV /dev/sdc1 VG foo1 lvm2 [<447.13 GiB / <447.13 GiB free] PV /dev/sdd1 VG foo1 lvm2 [<447.13 GiB / <447.13 GiB free] Total: 3 [<1.31 TiB] / in use: 3 [<1.31 TiB] / in no VG: 0 [0 ] Works on the latest build as well. Marking VERIFIED. kernel-5.14.0-306.el9 BUILT: Sat Apr 29 05:45:15 PM CEST 2023 lvm2-2.03.21-2.el9 BUILT: Thu May 25 12:03:04 AM CEST 2023 lvm2-libs-2.03.21-2.el9 BUILT: Thu May 25 12:03:04 AM CEST 2023 SCENARIO - vgimportclone_vdo_using_existing_vg_name: Create a vdo volume on a VG where and then vgimportclone that VG using the current existing name (bug 2168703) Creating VG on grant-01.6a2m.lab.eng.bos.redhat.com using PV(s) /dev/nvme0n1p1 /dev/sdd1 /dev/sde1 /dev/sdg1 /dev/sdh1 /dev/sdc1 vgcreate vdo_sanity /dev/nvme0n1p1 /dev/sdd1 /dev/sde1 /dev/sdg1 /dev/sdh1 /dev/sdc1 Volume group "vdo_sanity" successfully created creating VG on grant-01.6a2m.lab.eng.bos.redhat.com using PV(s) /dev/nvme1n1p1 vgcreate vdo_sanity1 /dev/nvme1n1p1 Volume group "vdo_sanity1" successfully created lvcreate --yes --type linear -n vdo_pool -L 10G vdo_sanity Logical volume "vdo_pool" created. lvconvert --yes --type vdo-pool -n vdo_lv -V100G vdo_sanity/vdo_pool The VDO volume can address 6 GB in 3 data slabs, each 2 GB. 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 "vdo_lv" created. Converted vdo_sanity/vdo_pool to VDO pool volume and created virtual vdo_sanity/vdo_lv VDO volume. WARNING: Converting logical volume vdo_sanity/vdo_pool to VDO pool volume with formatting. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) deactivating LV vdo_lv on grant-01.6a2m.lab.eng.bos.redhat.com lvchange --yes -an vdo_sanity/vdo_lv vgimportclone -n vdo_sanity /dev/nvme0n1p1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdg1 /dev/sdh1 lvremove -f vdo_sanity/vdo_lv Logical volume "vdo_lv" successfully removed. 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-2023:6633 |