summaryrefslogtreecommitdiff
path: root/tests/18imsm-r0_2d-takeover-r10_4d
diff options
context:
space:
mode:
authorKrzysztof Wojcik <krzysztof.wojcik@intel.com>2011-03-24 10:11:58 +1100
committerNeilBrown <neilb@suse.de>2011-03-24 10:11:58 +1100
commite53d022c726ffbc83b8bfc574df76bb7984d1982 (patch)
tree6728b97589667f5af831240711c8f36a44ad70c9 /tests/18imsm-r0_2d-takeover-r10_4d
parent3a5d04735bf36af7fdbca9e516472e14fb80d803 (diff)
FIX: Tests: raid0->raid10 without degradation
raid0->raid10 transition needs at least 2 spare devices. After level changing to raid10 recovery is triggered on failed (missing) disks. At the end of recovery process we have fully operational (not degraded) raid10 array. Initialy there was possibility to migrate raid0->raid10 without recovery triggering (it results degraded raid10). Now it is not possible. This patch adapt tests to new mdadm's behavior. Signed-off-by: Krzysztof Wojcik <krzysztof.wojcik@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'tests/18imsm-r0_2d-takeover-r10_4d')
-rw-r--r--tests/18imsm-r0_2d-takeover-r10_4d3
1 files changed, 2 insertions, 1 deletions
diff --git a/tests/18imsm-r0_2d-takeover-r10_4d b/tests/18imsm-r0_2d-takeover-r10_4d
index a1c395bd..0e77e5da 100644
--- a/tests/18imsm-r0_2d-takeover-r10_4d
+++ b/tests/18imsm-r0_2d-takeover-r10_4d
@@ -5,6 +5,7 @@
num_disks=2
device_list="$dev0 $dev1"
+spare_list="$dev2 $dev3"
# Before: RAID 0 volume, 2 disks, 256k chunk size
vol0_level=0
@@ -18,4 +19,4 @@ vol0_new_level=10
vol0_new_num_comps=$vol0_num_comps
vol0_new_chunk=128
-. tests/imsm-grow-template 0 1 1
+. tests/imsm-grow-template 0 1