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
447ba5f1c2
lvm2/test/shell/duplicate-pvs-md1.sh

647 lines
17 KiB
Bash
Raw Normal View History

tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
#!/usr/bin/env bash
# Copyright (C) 2012 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.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software Foundation,
# Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
# . different PV/VG's that happen to have the same PVID
# . a single PV/VG cloned to another device
# . dm wrapper around a PV
# . a single PV/VG cloned plus a dm wrapper (two separate dups of a PV)
SKIP_WITH_LVMPOLLD=1
RUNDIR="/run"
test -d "$RUNDIR" || RUNDIR="/var/run"
PVS_ONLINE_DIR="$RUNDIR/lvm/pvs_online"
VGS_ONLINE_DIR="$RUNDIR/lvm/vgs_online"
HINTS="$RUNDIR/lvm/hints"
_clear_online_files() {
# wait till udev is finished
aux udev_wait
rm -f "$PVS_ONLINE_DIR"/*
rm -f "$VGS_ONLINE_DIR"/*
}
. lib/inittest
test -f /proc/mdstat && grep -q raid1 /proc/mdstat || \
modprobe raid1 || skip
aux lvmconf 'devices/md_component_detection = 1'
# This stops lvm from asking udev if a dev is an md component.
# LVM will ask udev if a dev is an md component, but we don't
# want to rely on that ability in this test.
aux lvmconf 'devices/obtain_device_list_from_udev = 0'
aux extend_filter_LVMTEST "a|/dev/md|"
aux prepare_devs 4
# Create an unused PV so that there is at least one PV in the hints
# when the MD dev is stopped. If there are no PVs, the hints are
# empty, and the code falls back to scanning all, and we do not end
# up testing the code with hints actively used.
pvcreate "$dev3"
## Test variations:
# PV on md raid1|raid0, md_component_checks auto|start, mddev start|stopped,
# one leg disabled when mddev is stopped.
##########################################
# PV on an md raid1 device, auto+started
# md_component_checks: auto (not start)
# mddev: started (not stopped)
#
aux lvmconf 'devices/md_component_checks = "auto"'
aux prepare_md_dev 1 64 2 "$dev1" "$dev2"
sleep 4
cat /proc/mdstat
mddev=$(< MD_DEV)
pvdev=$(< MD_DEV_PV)
pvcreate "$mddev"
PVIDMD=`pvs $mddev --noheading -o uuid | tr -d - | awk '{print $1}'`
echo $PVIDMD
vgcreate $vg "$mddev"
lvcreate -n $lv1 -l 2 -an $vg
# pvs shows only the md dev as PV
pvs "$mddev"
not pvs "$dev1"
not pvs "$dev2"
pvs > out
grep $mddev out
not grep "$dev1" out
not grep "$dev2" out
grep "$mddev" $HINTS
not grep "$dev1" $HINTS
not grep "$dev2" $HINTS
# normal activation works
lvchange -ay $vg/$lv1
lvs -o active $vg |tee out || true
grep "active" out
vgchange -an $vg
# pvscan activation all works
_clear_online_files
pvscan --cache -aay
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
lvs -o active $vg |tee out || true
grep "active" out
vgchange -an $vg
# pvscan activation from mddev works
_clear_online_files
pvscan --cache -aay "$mddev"
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
lvs -o active $vg |tee out || true
grep "active" out
vgchange -an $vg
# pvscan activation from md components does nothing
_clear_online_files
pvscan --cache -aay "$dev1"
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
pvscan --cache -aay "$dev2"
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
lvs -o active $vg |tee out || true
not grep "active" out
vgchange -an $vg
vgremove -f $vg
aux cleanup_md_dev
##########################################
# PV on an md raid1 device, start+started
# md_component_checks: start (not auto)
# mddev: started (not stopped)
#
aux lvmconf 'devices/md_component_checks = "start"'
aux prepare_md_dev 1 64 2 "$dev1" "$dev2"
sleep 4
cat /proc/mdstat
mddev=$(< MD_DEV)
pvdev=$(< MD_DEV_PV)
pvcreate "$mddev"
PVIDMD=`pvs $mddev --noheading -o uuid | tr -d - | awk '{print $1}'`
echo $PVIDMD
vgcreate $vg "$mddev"
lvcreate -n $lv1 -l 2 -an $vg
# pvs shows only the md dev as PV
pvs "$mddev"
not pvs "$dev1"
not pvs "$dev2"
pvs > out
grep $mddev out
not grep "$dev1" out
not grep "$dev2" out
# N.B. in this case hints are disabled for duplicate pvs seen by scan
# it would be preferrable if this didn't happen as in auto mode, but it's ok.
# grep "$mddev" $HINTS
not grep "$dev1" $HINTS
not grep "$dev2" $HINTS
# normal activation works
lvchange -ay $vg/$lv1
lvs -o active $vg |tee out || true
grep "active" out
vgchange -an $vg
# pvscan activation all works
_clear_online_files
pvscan --cache -aay
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
lvs -o active $vg |tee out || true
grep "active" out
vgchange -an $vg
# pvscan activation from mddev works
_clear_online_files
pvscan --cache -aay "$mddev"
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
lvs -o active $vg |tee out || true
grep "active" out
vgchange -an $vg
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
# N.B. when the md dev (which is started) has not been scanned by
# pvscan, then pvscan --cache on the md component does not detect it's
# an md component, and marks the PVID online, then does activation,
# but the activation using the component fails because the component
# device is busy from being used in the md dev, and activation fails.
# The default behavior in auto mode is preferrable.
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
_clear_online_files
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
not pvscan --cache -aay "$dev1"
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
lvs -o active $vg |tee out || true
not grep "active" out
# pvscan activation from mddev first, then try from component which fails
_clear_online_files
pvscan --cache -aay "$mddev"
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
lvs -o active $vg |tee out || true
grep "active" out
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
not pvscan --cache -aay "$dev1"
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
vgchange -an $vg
vgremove -f $vg
aux cleanup_md_dev
##########################################
# PV on an md raid1 device, auto+stopped
# md_component_checks: auto (not start)
# mddev: stopped (not started)
#
aux lvmconf 'devices/md_component_checks = "auto"'
aux prepare_md_dev 1 64 2 "$dev1" "$dev2"
sleep 4
cat /proc/mdstat
mddev=$(< MD_DEV)
pvdev=$(< MD_DEV_PV)
pvcreate "$mddev"
PVIDMD=`pvs $mddev --noheading -o uuid | tr -d - | awk '{print $1}'`
echo $PVIDMD
vgcreate $vg "$mddev"
lvcreate -n $lv1 -l 2 -an $vg
mdadm --stop "$mddev"
cat /proc/mdstat
# pvs does not show the PV
not pvs "$mddev"
not pvs "$dev1"
not pvs "$dev2"
pvs > out
not grep $mddev out
not grep "$dev1" out
not grep "$dev2" out
pvscan --cache
not grep "$mddev" $HINTS
not grep "$dev1" $HINTS
not grep "$dev2" $HINTS
# the vg is not seen, normal activation does nothing
not lvchange -ay $vg/$lv1
not lvs $vg
# pvscan activation all does nothing
_clear_online_files
pvscan --cache -aay
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
# pvscan activation from md components does nothing
_clear_online_files
pvscan --cache -aay "$dev1"
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
pvscan --cache -aay "$dev2"
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
aux cleanup_md_dev
##########################################
# PV on an md raid1 device, start+stopped
# md_component_checks: start (not auto)
# mddev: stopped (not started)
#
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
# N.B. This test case is just characterizing the current behavior, even
# though the behavior it's testing for is not what we'd want to happen.
# In this scenario, we have disabled/avoided everything that would
# lead lvm to discover that dev1 is an md component, so dev1 is used
# as the PV. Multiple default settings need to be changed to get to
# this unwanted behavior (md_component_checks,
# obtain_device_list_from_udev), and other conditions also
# need to be true (md device stopped).
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
aux lvmconf 'devices/md_component_checks = "start"'
wipefs -a "$dev1" "$dev2"
aux prepare_md_dev 1 64 2 "$dev1" "$dev2"
sleep 4
cat /proc/mdstat
mddev=$(< MD_DEV)
pvdev=$(< MD_DEV_PV)
pvcreate "$mddev"
PVIDMD=`pvs $mddev --noheading -o uuid | tr -d - | awk '{print $1}'`
echo $PVIDMD
vgcreate $vg "$mddev"
lvcreate -n $lv1 -l 2 -an $vg
mdadm --stop "$mddev"
cat /proc/mdstat
# pvs does not show the PV
not pvs "$mddev"
not pvs "$dev1"
not pvs "$dev2"
pvs > out
not grep $mddev out
not grep "$dev1" out
not grep "$dev2" out
pvscan --cache
not grep "$mddev" $HINTS
not grep "$dev1" $HINTS
not grep "$dev2" $HINTS
# the vg is not seen, normal activation does nothing
not lvchange -ay $vg/$lv1
not lvs $vg
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
# pvscan activation all does nothing because both legs are
# seen as duplicates which triggers md component check which
# eliminates the devs
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
_clear_online_files
pvscan --cache -aay
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
_clear_online_files
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
pvscan --cache -aay "$dev1"
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
# N.B. not good to activate from component, but result of "start" setting
# Other commands will not see the vg at this point because they'll
# recognize the md components and ignore them (where pvscan is special due
# to it not scanning all devs and not seeing the duplicates and not
# detecting the components.)
# disable dev2 so other cmds don't see dups and we can deactivate the vg
aux disable_dev "$dev2"
vgchange -an $vg
aux enable_dev "$dev2"
aux udev_wait
cat /proc/mdstat
# for some reason enabling dev2 starts an odd md dev
mdadm --stop "$mddev" || true
mdadm --stop --scan
cat /proc/mdstat
wipefs -a "$dev1" || true
wipefs -a "$dev2" || true
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
##########################################
# PV on an md raid1 device, start+stopped
# md_component_checks: start (not auto)
# mddev: stopped (not started)
# only one raid image online
#
# N.B. This test case is just characterizing the current behavior, even
# though the behavior it's testing for is not what we'd want to happen.
# In this scenario, we have disabled/avoided everything that would
# lead lvm to discover that dev1 is an md component, so dev1 is used
# as the PV. Multiple default settings need to be changed to get to
# this unwanted behavior (md_component_checks,
# obtain_device_list_from_udev), and multiple other conditions also
# need to be true (md device stopped, only one leg visible).
aux lvmconf 'devices/md_component_checks = "start"'
wipefs -a "$dev1" "$dev2"
aux prepare_md_dev 1 64 2 "$dev1" "$dev2"
sleep 4
cat /proc/mdstat
mddev=$(< MD_DEV)
pvdev=$(< MD_DEV_PV)
pvcreate "$mddev"
PVIDMD=`pvs $mddev --noheading -o uuid | tr -d - | awk '{print $1}'`
echo $PVIDMD
vgcreate $vg "$mddev"
lvcreate -n $lv1 -l 2 -an $vg
mdadm --stop "$mddev"
cat /proc/mdstat
# disable one leg of the md device, with raid1 this means duplicates
# will not be seen for the legs. duplicate handling can trigger
# md component detection, so no duplicates means md components may
# not be detected as easily.
aux disable_dev "$dev2"
# pvs does not show the PV
not pvs "$mddev"
pvs "$dev1"
not pvs "$dev2"
pvs > out
not grep $mddev out
grep "$dev1" out
not grep "$dev2" out
pvscan --cache
not grep "$mddev" $HINTS
grep "$dev1" $HINTS
not grep "$dev2" $HINTS
lvchange -ay $vg/$lv1
lvs $vg
vgchange -an $vg
_clear_online_files
pvscan --cache -aay
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
# N.B. not good to activate from component, but result of "start" setting
lvs -o active $vg |tee out || true
grep "active" out
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
vgchange -an $vg
_clear_online_files
pvscan --cache -aay "$dev1"
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
# N.B. not good to activate from component, but result of "start" setting
lvs -o active $vg |tee out || true
grep "active" out
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
vgchange -an $vg
aux enable_dev "$dev2"
aux udev_wait
cat /proc/mdstat
# for some reason enabling dev2 starts an odd md dev
mdadm --stop "$mddev" || true
mdadm --stop --scan
cat /proc/mdstat
wipefs -a "$dev1" || true
wipefs -a "$dev2" || true
##########################################
# PV on an md raid1 device, auto+stopped
# md_component_checks: auto (not start)
# mddev: stopped (not started)
# only one raid image online
#
aux lvmconf 'devices/md_component_checks = "auto"'
aux prepare_md_dev 1 64 2 "$dev1" "$dev2"
sleep 4
cat /proc/mdstat
mddev=$(< MD_DEV)
pvdev=$(< MD_DEV_PV)
pvcreate "$mddev"
PVIDMD=`pvs $mddev --noheading -o uuid | tr -d - | awk '{print $1}'`
echo $PVIDMD
vgcreate $vg "$mddev"
lvcreate -n $lv1 -l 2 -an $vg
mdadm --stop "$mddev"
cat /proc/mdstat
# disable one leg
aux disable_dev "$dev2"
# pvs does not show the PV
not pvs "$mddev"
not pvs "$dev1"
not pvs "$dev2"
pvs > out
not grep $mddev out
not grep "$dev1" out
not grep "$dev2" out
pvscan --cache
not grep "$mddev" $HINTS
not grep "$dev1" $HINTS
not grep "$dev2" $HINTS
# the vg is not seen, normal activation does nothing
not lvchange -ay $vg/$lv1
not lvs $vg
# pvscan activation all does nothing
_clear_online_files
pvscan --cache -aay
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
# pvscan activation from md components does nothing
_clear_online_files
pvscan --cache -aay "$dev1"
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
pvscan --cache -aay "$dev2"
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
aux enable_dev "$dev2"
aux udev_wait
cat /proc/mdstat
# for some reason enabling dev2 starts an odd md dev
mdadm --stop "$mddev" || true
mdadm --stop --scan
cat /proc/mdstat
wipefs -a "$dev1" || true
wipefs -a "$dev2" || true
##########################################
# PV on an md raid1 device, auto+stopped
# md_component_checks: auto (not start)
# mddev: stopped (not started)
# three raid images
#
aux lvmconf 'devices/md_component_checks = "auto"'
aux prepare_md_dev 1 64 3 "$dev1" "$dev2" "$dev4"
sleep 4
cat /proc/mdstat
mddev=$(< MD_DEV)
pvdev=$(< MD_DEV_PV)
pvcreate "$mddev"
PVIDMD=`pvs $mddev --noheading -o uuid | tr -d - | awk '{print $1}'`
echo $PVIDMD
vgcreate $vg "$mddev"
lvcreate -n $lv1 -l 2 -an $vg
mdadm --stop "$mddev"
cat /proc/mdstat
# pvs does not show the PV
not pvs "$mddev"
not pvs "$dev1"
not pvs "$dev2"
not pvs "$dev4"
pvs > out
not grep $mddev out
not grep "$dev1" out
not grep "$dev2" out
not grep "$dev4" out
pvscan --cache
not grep "$mddev" $HINTS
not grep "$dev1" $HINTS
not grep "$dev2" $HINTS
not grep "$dev4" $HINTS
# the vg is not seen, normal activation does nothing
not lvchange -ay $vg/$lv1
not lvs $vg
# pvscan activation all does nothing
_clear_online_files
pvscan --cache -aay
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
# pvscan activation from md components does nothing
_clear_online_files
pvscan --cache -aay "$dev1"
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
pvscan --cache -aay "$dev2"
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
pvscan --cache -aay "$dev4"
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
aux cleanup_md_dev
##########################################
# PV on an md raid1 device, start+stopped
# md_component_checks: start (not auto)
# mddev: stopped (not started)
# three raid images
aux lvmconf 'devices/md_component_checks = "start"'
wipefs -a "$dev1" "$dev2" "$dev4"
aux prepare_md_dev 1 64 3 "$dev1" "$dev2" "$dev4"
sleep 4
cat /proc/mdstat
mddev=$(< MD_DEV)
pvdev=$(< MD_DEV_PV)
pvcreate "$mddev"
PVIDMD=`pvs $mddev --noheading -o uuid | tr -d - | awk '{print $1}'`
echo $PVIDMD
vgcreate $vg "$mddev"
lvcreate -n $lv1 -l 2 -an $vg
mdadm --stop "$mddev"
cat /proc/mdstat
# pvs does not show the PV
not pvs "$mddev"
not pvs "$dev1"
not pvs "$dev2"
not pvs "$dev4"
pvs > out
not grep $mddev out
not grep "$dev1" out
not grep "$dev2" out
not grep "$dev4" out
pvscan --cache
not grep "$mddev" $HINTS
not grep "$dev1" $HINTS
not grep "$dev2" $HINTS
not grep "$dev4" $HINTS
# the vg is not seen, normal activation does nothing
not lvchange -ay $vg/$lv1
not lvs $vg
# pvscan activation all does nothing
_clear_online_files
pvscan --cache -aay
not ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
not ls "$RUNDIR/lvm/vgs_online/$vg"
_clear_online_files
pvscan --cache -aay "$dev1" || true
ls "$RUNDIR/lvm/pvs_online/$PVIDMD"
ls "$RUNDIR/lvm/vgs_online/$vg"
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
# N.B. not good to activate from component, but result of "start" setting
# Scanning the other two legs sees existing pv online file and warns about
# duplicate PVID, exiting with error:
not pvscan --cache -aay "$dev2"
not pvscan --cache -aay "$dev4"
# Have to disable other legs so we can deactivate since
# vgchange will detect and eliminate the components due
# to duplicates and not see the vg.
aux disable_dev "$dev2"
aux disable_dev "$dev4"
vgchange -an $vg
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
pvscan: avoid full scan for activation When an online PV completed a VG, the standard activation functions were used to activate the VG. These functions use a full scan of all devs. When many pvscans are run during startup and need to activate many VGs, scanning all devs from all the pvscans can take a long time. Optimize VG activation in pvscan to scan only the devs in the VG being activated. This makes use of the online file info that was used to determine the VG was complete. The downside of this approach is that pvscan activation will not detect duplicate PVs and block activation, where a normal activation command (which scans all devices) would.
2019-08-27 01:07:18 +03:00
aux enable_dev "$dev2"
aux enable_dev "$dev4"
aux udev_wait
cat /proc/mdstat
# for some reason enabling dev2 starts an odd md dev
mdadm --stop "$mddev" || true
mdadm --stop --scan
cat /proc/mdstat
wipefs -a "$dev1" || true
wipefs -a "$dev2" || true
wipefs -a "$dev4" || true
tests: duplicate-pvs-md Testing duplicate PV handling for various md device setups/states.
2019-08-16 21:22:58 +03:00
Copy Permalink