summaryrefslogtreecommitdiffstats
path: root/test/shell/lvcreate-repair.sh
diff options
context:
space:
mode:
authorPetr Rockai <prockai@redhat.com>2012-02-23 14:55:29 +0000
committerPetr Rockai <prockai@redhat.com>2012-02-23 14:55:29 +0000
commitd4836062ff55800080de0279bac491291ab75621 (patch)
tree13a2502d0539d2c2a3a4e8a810c79c7e96548e8a /test/shell/lvcreate-repair.sh
parentf84d6048cf3385c5fdb8de96dfc9d87463ab8fb5 (diff)
downloadlvm2-d4836062ff55800080de0279bac491291ab75621.tar.gz
lvm2-d4836062ff55800080de0279bac491291ab75621.tar.xz
lvm2-d4836062ff55800080de0279bac491291ab75621.zip
Add a vgscan to lvcreate-repair.sh. The old test applied device filter hacks to
make devices invisible to lvm, but the behaviour of those is slightly different than of actual missing devices. Running vgscan after re-enabling the device triggers a metadata repair which is not done by vgremove -ff. This is not a regression, merely an odd behaviour that has been around even before lvmetad.
Diffstat (limited to 'test/shell/lvcreate-repair.sh')
-rw-r--r--test/shell/lvcreate-repair.sh1
1 files changed, 1 insertions, 0 deletions
diff --git a/test/shell/lvcreate-repair.sh b/test/shell/lvcreate-repair.sh
index 55cd1ae6..12da518c 100644
--- a/test/shell/lvcreate-repair.sh
+++ b/test/shell/lvcreate-repair.sh
@@ -38,6 +38,7 @@ for i in $dev1 $dev2 $dev3 ; do
check lv_exists $vg $lv2
aux enable_dev $i $j
+ vgscan
test $i != $dev1 && check lv_exists $vg $lv1
check lv_exists $vg $lv2