tests, imsm: Set new_num_disks value corectly to perform expected size calculations
In some migration tests, variable new_num_disks should be set to expected number of disks after migration. This is required for proper expected size calculation. Pass new_num_disks variable during test execution for: - 16imsm-r0_3d-migrate-r5_4d - 18imsm-r1_2d-takeover-r0_1d - 16imsm-r0_5d-migrate-r5_6d Signed-off-by: Michal Zylowski <michal.zylowski@intel.com> Signed-off-by: Jes Sorensen <jsorensen@fb.com>
This commit is contained in:
parent
b202e322c1
commit
2b2ccdc04b
|
@ -15,6 +15,7 @@ vol0_offset=0
|
|||
|
||||
# After: RAID 5, 4 disks, 64k chunk size
|
||||
vol0_new_level=5
|
||||
new_num_disks=4
|
||||
vol0_new_num_comps=$num_disks
|
||||
vol0_new_chunk=64
|
||||
|
||||
|
|
|
@ -17,5 +17,6 @@ vol0_offset=0
|
|||
vol0_new_level=5
|
||||
vol0_new_num_comps=$num_disks
|
||||
vol0_new_chunk=64
|
||||
new_num_disks=6
|
||||
|
||||
. tests/imsm-grow-template 0 1
|
||||
|
|
|
@ -17,6 +17,6 @@ vol0_offset=0
|
|||
vol0_new_level=0
|
||||
vol0_new_num_comps=1
|
||||
vol0_new_chunk=64
|
||||
new_num_disks=0
|
||||
new_num_disks=1
|
||||
|
||||
. tests/imsm-grow-template 0 1
|
||||
|
|
Loading…
Reference in New Issue