lvm2/test/shell/vg-raid-takeover-4.sh

#!/usr/bin/env bash

# Copyright (C) 2023 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

test_description='Test VG takeover with raid LVs'

CONTINUE_ELSEWHERE=y
PREPARE_DEVS=4

. ./shell/vg-raid-takeover-1.sh

# unhide_dev
# the device reappears before the LVs are repaired
# and before the missing dev is removed from the vg

aux unhide_dev "$dev1"

pvs -o+missing
vgs -o+systemid,partial $vg
lvs -a -o+devices $vg

vgextend --restoremissing $vg "$dev1"


test_check_mount


vgchange -an $vg
vgremove -f $vg
tests: vg-raid-takeover Different sequences of steps that could be used to handle raid LVs after VG takeover (what would happen in cluster failover) combined with the loss of a disk. 2023-02-08 00:25:46 +03:00			`#!/usr/bin/env bash`

tests: lower demand for disk resources Convert test to use a single skeleton and only different pieces keep in separate tests. Lower raid disk usage to smaller size and switch to ext4 as way less demanding fileystem. 2023-04-04 15:44:47 +03:00			`# Copyright (C) 2023 Red Hat, Inc. All rights reserved.`
tests: vg-raid-takeover Different sequences of steps that could be used to handle raid LVs after VG takeover (what would happen in cluster failover) combined with the loss of a disk. 2023-02-08 00:25:46 +03:00			`#`
			`# 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`

			`test_description='Test VG takeover with raid LVs'`

tests: lower demand for disk resources Convert test to use a single skeleton and only different pieces keep in separate tests. Lower raid disk usage to smaller size and switch to ext4 as way less demanding fileystem. 2023-04-04 15:44:47 +03:00			`CONTINUE_ELSEWHERE=y`
			`PREPARE_DEVS=4`
tests: vg-raid-takeover Different sequences of steps that could be used to handle raid LVs after VG takeover (what would happen in cluster failover) combined with the loss of a disk. 2023-02-08 00:25:46 +03:00
tests: lower demand for disk resources Convert test to use a single skeleton and only different pieces keep in separate tests. Lower raid disk usage to smaller size and switch to ext4 as way less demanding fileystem. 2023-04-04 15:44:47 +03:00			`. ./shell/vg-raid-takeover-1.sh`
tests: vg-raid-takeover Different sequences of steps that could be used to handle raid LVs after VG takeover (what would happen in cluster failover) combined with the loss of a disk. 2023-02-08 00:25:46 +03:00
			`# unhide_dev`
			`# the device reappears before the LVs are repaired`
			`# and before the missing dev is removed from the vg`

			`aux unhide_dev "$dev1"`

			`pvs -o+missing`
			`vgs -o+systemid,partial $vg`
			`lvs -a -o+devices $vg`

			`vgextend --restoremissing $vg "$dev1"`


tests: lower demand for disk resources Convert test to use a single skeleton and only different pieces keep in separate tests. Lower raid disk usage to smaller size and switch to ext4 as way less demanding fileystem. 2023-04-04 15:44:47 +03:00			`test_check_mount`
tests: vg-raid-takeover Different sequences of steps that could be used to handle raid LVs after VG takeover (what would happen in cluster failover) combined with the loss of a disk. 2023-02-08 00:25:46 +03:00

			`vgchange -an $vg`
			`vgremove -f $vg`