shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-22 17:35:59 +03:00
Code Releases Activity
59b46fc8cd
lvm2/test/shell/duplicate-vgrename.sh

305 lines
6.0 KiB
Bash
Raw Normal View History

lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
#!/usr/bin/env bash
# Copyright (C) 2008-2013 Red Hat, Inc. All rights reserved.
#
# This copyrighted material is made available to anyone wishing to use,
# modify, copy, or redistribute it subject to the terms and conditions
# of the GNU General Public License v.2.
SKIP_WITH_LVMLOCKD=1
SKIP_WITH_LVMPOLLD=1
. lib/inittest
aux prepare_devs 4
# a. 0 local, 1 foreign
# setup
vgcreate $vg1 "$dev1"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID1=$(vgs --noheading -o vg_uuid $vg1 | xargs)
vgchange -y --systemid "other" $vg1
not vgrename $vg1 $vg2
vgs --foreign -o+uuid |tee out
grep $UUID1 out
not vgrename $UUID1 $vg2
vgs --foreign -o+uuid |tee out
grep $UUID1 out
lvs --foreign
aux wipefs_a "$dev1"
# b. 0 local, 2 foreign
# setup
vgcreate $vg1 "$dev1"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID1=$(vgs --noheading -o vg_uuid $vg1 | xargs)
vgchange -y --systemid "other" $vg1
aux disable_dev "$dev1"
vgcreate $vg1 "$dev2"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID2=$(vgs --noheading -o vg_uuid $vg1 | xargs)
vgchange -y --systemid "other2" $vg1
aux enable_dev "$dev1"
not vgrename $vg1 $vg2
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
not grep $vg2 out
grep $UUID1 out
grep $UUID2 out
not vgrename $UUID1 $vg2
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
not grep $vg2 out
grep $UUID1 out
grep $UUID2 out
lvs --foreign
tests: updates Pass more args with some 'aux' commands: wipefs_a, enable_dev, disable_dev (so it's a bit more efficient using single udev_wait call). Use prepare_vg instead of prepare_pvs.
2023-07-15 11:39:56 +03:00
aux wipefs_a "$dev1" "$dev2"
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
# c. 1 local, 1 foreign
# setup
vgcreate $vg1 "$dev1"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID1=$(vgs --noheading -o vg_uuid $vg1 | xargs)
aux disable_dev "$dev1"
vgcreate $vg1 "$dev2"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID2=$(vgs --noheading -o vg_uuid $vg1 | xargs)
vgchange -y --systemid "other" $vg1
aux enable_dev "$dev1"
vgrename $vg1 $vg2
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $UUID1 out
grep $UUID2 out
not vgrename $vg2 $vg1
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $UUID1 out
grep $UUID2 out
lvs --foreign
tests: updates Pass more args with some 'aux' commands: wipefs_a, enable_dev, disable_dev (so it's a bit more efficient using single udev_wait call). Use prepare_vg instead of prepare_pvs.
2023-07-15 11:39:56 +03:00
aux wipefs_a "$dev1" "$dev2"
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
# d. 1 local, 2 foreign
# setup
vgcreate $vg1 "$dev1"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID1=$(vgs --noheading -o vg_uuid $vg1 | xargs)
aux disable_dev "$dev1"
vgcreate $vg1 "$dev2"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID2=$(vgs --noheading -o vg_uuid $vg1 | xargs)
vgchange -y --systemid "other" $vg1
aux disable_dev "$dev2"
vgcreate $vg1 "$dev3"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID3=$(vgs --noheading -o vg_uuid $vg1 | xargs)
vgchange -y --systemid "other2" $vg1
tests: updates Pass more args with some 'aux' commands: wipefs_a, enable_dev, disable_dev (so it's a bit more efficient using single udev_wait call). Use prepare_vg instead of prepare_pvs.
2023-07-15 11:39:56 +03:00
aux enable_dev "$dev1" "$dev2"
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
vgrename $vg1 $vg2
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
not vgrename $vg2 $vg1
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
lvs --foreign
tests: updates Pass more args with some 'aux' commands: wipefs_a, enable_dev, disable_dev (so it's a bit more efficient using single udev_wait call). Use prepare_vg instead of prepare_pvs.
2023-07-15 11:39:56 +03:00
aux wipefs_a "$dev1" "$dev2" "$dev3"
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
# e. 2 local, 0 foreign
# setup
vgcreate $vg1 "$dev1"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID1=$(vgs --noheading -o vg_uuid $vg1 | xargs)
aux disable_dev "$dev1"
vgcreate $vg1 "$dev2"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n ${lv1}_b -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID2=$(vgs --noheading -o vg_uuid $vg1 | xargs)
aux enable_dev "$dev1"
not vgrename $vg1 $vg2
vgs -o+uuid |tee out
lvs --foreign
grep $vg1 out
not grep $vg2 out
grep $UUID1 out
grep $UUID2 out
vgrename $UUID1 $vg2
vgs -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $UUID1 out
grep $UUID2 out
not vgrename $UUID2 $vg2
vgs -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $UUID1 out
grep $UUID2 out
lvs --foreign
tests: updates Pass more args with some 'aux' commands: wipefs_a, enable_dev, disable_dev (so it's a bit more efficient using single udev_wait call). Use prepare_vg instead of prepare_pvs.
2023-07-15 11:39:56 +03:00
aux wipefs_a "$dev1" "$dev2"
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
# f. 2 local, 1 foreign
# setup
vgcreate $vg1 "$dev1"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID1=$(vgs --noheading -o vg_uuid $vg1 | xargs)
aux disable_dev "$dev1"
vgcreate $vg1 "$dev2"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n ${lv1}_b -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID2=$(vgs --noheading -o vg_uuid $vg1 | xargs)
aux disable_dev "$dev2"
vgcreate $vg1 "$dev3"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID3=$(vgs --noheading -o vg_uuid $vg1 | xargs)
vgchange -y --systemid "other" $vg1
tests: updates Pass more args with some 'aux' commands: wipefs_a, enable_dev, disable_dev (so it's a bit more efficient using single udev_wait call). Use prepare_vg instead of prepare_pvs.
2023-07-15 11:39:56 +03:00
aux enable_dev "$dev1" "$dev2"
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
lvs --foreign
not vgrename $vg1 $vg2
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
not grep $vg2 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
vgrename $UUID1 $vg2
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
vgrename $vg1 $vg3
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $vg3 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
not vgrename $vg2 $vg1
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $vg3 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
not vgrename $vg2 $vg3
vgs --foreign -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $vg3 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
lvs --foreign
tests: updates Pass more args with some 'aux' commands: wipefs_a, enable_dev, disable_dev (so it's a bit more efficient using single udev_wait call). Use prepare_vg instead of prepare_pvs.
2023-07-15 11:39:56 +03:00
aux wipefs_a "$dev1" "$dev2" "$dev3"
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
# g. 3 local, 0 foreign
# setup
vgcreate $vg1 "$dev1"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n $lv1 -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID1=$(vgs --noheading -o vg_uuid $vg1 | xargs)
aux disable_dev "$dev1"
vgcreate $vg1 "$dev2"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n ${lv1}_b -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID2=$(vgs --noheading -o vg_uuid $vg1 | xargs)
aux disable_dev "$dev2"
vgcreate $vg1 "$dev3"
tests: set skipping autoactivation On test system with 'default' filter (aka accept all) test after enabling device can suffer from automatic system activation - so for created LVs setup skipping this automatic activation. This should prevent getting LVs into table with pvscan service.
2020-09-01 23:45:17 +03:00
lvcreate -n ${lv1}_c -l1 -ky -an $vg1
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
UUID3=$(vgs --noheading -o vg_uuid $vg1 | xargs)
tests: updates Pass more args with some 'aux' commands: wipefs_a, enable_dev, disable_dev (so it's a bit more efficient using single udev_wait call). Use prepare_vg instead of prepare_pvs.
2023-07-15 11:39:56 +03:00
aux enable_dev "$dev1" "$dev2"
lvmcache: rework handling of VGs with duplicate vgnames The previous method of managing duplicate vgnames prevented vgreduce from working if a foreign vg with the same name existed.
2020-01-28 20:47:37 +03:00
not vgrename $vg1 $vg2
vgs -o+uuid |tee out
lvs --foreign
grep $vg1 out
not grep $vg2 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
vgrename $UUID1 $vg2
vgs -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
not vgrename $vg1 $vg2
vgs -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
not vgrename $vg1 $vg3
vgs -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
not grep $vg3 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
not vgrename $UUID2 $vg2
vgs -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
not grep $vg3 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
vgrename $UUID2 $vg3
vgs -o+uuid |tee out
lvs --foreign
grep $vg1 out
grep $vg2 out
grep $vg3 out
grep $UUID1 out
grep $UUID2 out
grep $UUID3 out
lvs --foreign
Copy Permalink