Red Hat Bugzilla – Bug 433479
vgsplit may fail to delete old VG dev entries
Last modified: 2008-06-04 16:46:36 EDT
Description of problem:
One of our regression tests is to vgsplit out pvs to a new vg and then split it
back to the orginal vg. Sometimes we need up spliting out all the pvs in the vg
so it becomes more of a rename operation. In this case it failed to split back
because the device entry from the first vg was not deleted.
[lvm_single_config] VOLUME SPLIT of in use pvs from stripe_5_3474 to split_359
[lvm_single_config] deactivating volume group
[lvm_single_config] checking that new vg split_359 exists on hayes-01
[lvm_single_config] VOLUME SPLIT split_359 back into stripe_5_3474 on hayes-01
[lvm_single_config] /dev/stripe_5_3474: already exists in filesystem
[lvm_single_config] New volume group name "stripe_5_3474" is invalid
[lvm_single_config] vgsplit failed:
[root@hayes-01 ~]# ls -lrt /dev/stripe_5_3474/
lrwxrwxrwx 1 root root 31 Feb 18 19:34 snap1 -> /dev/mapper/stripe_5_3474-snap1
lrwxrwxrwx 1 root root 31 Feb 18 19:34 snap0 -> /dev/mapper/stripe_5_3474-snap0
However, it I choose a different vg name to split to, the operation works.
Here are the lvs currently in the vg:
snap0 split_359 swi--- 100.00M stripe_5_34740
snap1 split_359 swi--- 48.00M stripe_5_34740
stripe_5_34740 split_359 owi--- 7.39T
Version-Release number of selected component (if applicable):
Corey can you show me how to run this test or give me the cmdlines that I can
Also, I assume this is a regression from the previous release?
I was unable to reproduce this bug in the lastest 4.7 rpms, closing.