| Summary: | vgsplit attempt of external origin volume fail with "Internal error: Referenced LV not listed in VG" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Roman Bednář <rbednar> |
| Component: | lvm2 | Assignee: | Heinz Mauelshagen <heinzm> |
| lvm2 sub component: | Command-line tools | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | agk, cmarthal, heinzm, jbrassow, mnavrati, msnitzer, prajnoha, prockai, thornber, zkabelac |
| Version: | 7.3 | Keywords: | Regression, TestBlocker |
| Target Milestone: | rc | Flags: | heinzm:
needinfo-
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.164-3.el7 | Doc Type: | No Doc Update |
| Doc Text: |
Intra-release bug, no documentation needed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 04:17: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: | |
|
Description
Roman Bednář
2016-08-16 13:03:27 UTC
Not reproducing this here, neither on upstream 2.02.164, nor on RHEL7.3. Is this a fresh setup creating the origin and the snapshots and then vgsplit immediately fails (which I tried as a reproducer)? [root@work bin]# lvs -o+devices LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert Devices root fedora_vm20 -wi-ao---- 45.63g /dev/vda2(992) swap fedora_vm20 -wi-ao---- 3.88g /dev/vda2(0) EXT seven ori------- 64.00m /dev/sdb(263168) pool seven twi---tz-- 512.00m pool_tdata(0) snap1 seven Vwi---tz-- 64.00m pool EXT snap2 seven Vwi---tz-- 64.00m pool EXT snap3 seven Vwi---tz-- 64.00m pool EXT [root@work bin]# vgsplit -n EXT seven ten Can't split pool data and metadata pool between two Volume Groups. Fixed test as of comment #3 to actually allocate the external origin on different PV from the pool LVs and that leads to the initially reported: [root@work ~]# vgsplit -n EXT seven ten Internal error: Referenced LV EXT not listed in VG ten. Internal error: Referenced PV /dev/sdb not listed in VG ten. Upstream commit c0a0eedf2e572b99e40384e68e3d5f8fba6f0ae5 Fix verified (once again) in the latest rpms. lvm2-2.02.164-2.el7 BUILT: Tue Aug 16 05:43:50 CDT 2016 lvm2-libs-2.02.164-2.el7 BUILT: Tue Aug 16 05:43:50 CDT 2016 lvm2-cluster-2.02.164-2.el7 BUILT: Tue Aug 16 05:43:50 CDT 2016 [root@host-127 ~]# lvs -a -o +devices LV VG Attr LSize Pool Origin Devices EXT seven ori------- 1.00g /dev/sde1(0) extorigin seven Vwi---tz-- 1.00g pool EXT [lvol0_pmspare] seven ewi------- 4.00m /dev/sdb1(0) pool seven twi---tz-- 100.00m pool_tdata(0) [pool_tdata] seven Twi------- 100.00m /dev/sdb1(1) [pool_tmeta] seven ewi------- 4.00m /dev/sdb1(26) snap1 seven Vwi---tz-k 1.00g pool extorigin snap2 seven Vwi---tz-k 1.00g pool extorigin snap3 seven Vwi---tz-k 1.00g pool extorigin [root@host-127 ~]# vgsplit -n EXT seven ten Internal error: Referenced LV EXT not listed in VG ten. Internal error: Referenced PV /dev/sde1 not listed in VG ten. lvm2-2.02.164-3.el7 BUILT: Wed Aug 24 05:20:41 CDT 2016 lvm2-libs-2.02.164-3.el7 BUILT: Wed Aug 24 05:20:41 CDT 2016 lvm2-cluster-2.02.164-3.el7 BUILT: Wed Aug 24 05:20:41 CDT 2016 [root@host-117 ~]# lvs -a -o +devices LV VG Attr LSize Pool Origin Devices EXT seven ori------- 1.00g /dev/sda1(0) extorigin seven Vwi---tz-- 1.00g pool EXT [lvol0_pmspare] seven ewi------- 4.00m /dev/sdf1(0) pool seven twi---tz-- 100.00m pool_tdata(0) [pool_tdata] seven Twi------- 100.00m /dev/sdf1(1) [pool_tmeta] seven ewi------- 4.00m /dev/sdf1(26) snap1 seven Vwi---tz-k 1.00g pool extorigin snap2 seven Vwi---tz-k 1.00g pool extorigin snap3 seven Vwi---tz-k 1.00g pool extorigin [root@host-117 ~]# vgsplit -n EXT seven ten Can't split external origin EXT and pool pool between two Volume Groups. 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 |