Red Hat Bugzilla – Bug 246115
vgsplit should allow all pvs in vg to be split out (vgrename)
Last modified: 2013-02-28 23:05:48 EST
Description of problem: Currently if you try to split out all the pvs from a vg with out much space left in the pvs, you'll get the following error: "Cannot split: Nowhere to store metadata for new Volume Group" [root@taft-01 ~]# pvscan PV /dev/sdb3 VG stripe_3_1422 lvm2 [90.82 GB / 0 free] PV /dev/sdb2 VG stripe_3_1422 lvm2 [90.82 GB / 48.00 MB free] PV /dev/sdb1 VG stripe_3_1422 lvm2 [90.82 GB / 52.00 MB free] [root@taft-01 ~]# vgsplit stripe_3_1422 split_65 /dev/sdb3 /dev/sdb2 /dev/sdb1 Cannot split: Nowhere to store metadata for new Volume Group Version-Release number of selected component (if applicable): lvm2-2.02.26-1.el5 How reproducible: everytime
Fixed upstream.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
In lvm2-2.02.30-1.el5.
The fix for this bug has been verified in lvm2-2.02.32-2.el5, however I'm curious about an extra message that is given when running this cmd. [root@hayes-03 ~]# pvscan PV /dev/etherd/e1.1p1 VG corey lvm2 [1.27 TB / 0 free] PV /dev/etherd/e1.1p2 VG corey lvm2 [1.27 TB / 0 free] PV /dev/etherd/e1.1p3 VG corey lvm2 [1.27 TB / 0 free] PV /dev/etherd/e1.1p4 VG corey lvm2 [1.27 TB / 0 free] PV /dev/etherd/e1.1p5 VG corey lvm2 [1.27 TB / 0 free] PV /dev/etherd/e1.1p6 VG corey lvm2 [1.27 TB / 2.41 GB free] PV /dev/sda2 VG VolGroup00 lvm2 [74.38 GB / 0 free] PV /dev/etherd/e1.1p7 lvm2 [1.27 TB] Total: 8 [8.94 TB] / in use: 7 [7.67 TB] / in no VG: 1 [1.27 TB] [root@hayes-03 ~]# vgsplit corey feist /dev/etherd/e1.1p[123456] Logical volumes in "corey" must be inactive [root@hayes-03 ~]# vgchange -an corey 0 logical volume(s) in volume group "corey" now active # Why is 'Volume group "feist" not found' reported, should that be a new bug? [root@hayes-03 ~]# vgsplit corey feist /dev/etherd/e1.1p[123456] Volume group "feist" not found New volume group "feist" successfully split from "corey" [root@hayes-03 ~]# lvscan inactive '/dev/feist/lv' [7.60 TB] inherit
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0378.html