It requires patch from, otherwise it fails anyway: "mdadm/grow: adding a test to ensure resize was required" https://www.spinics.net/lists/raid/msg59743.html Since: 19ceb16dafb7df98ff90298008d4488dc93b370a ("Grow: add raid10 reshape.") # mdadm mdadm-3.2.5-120-g19ceb16 Since: 3ea7daa5d7fde47cd41f4d56c2deb949114da9d6 ("md/raid10: add reshape support") # linux v3.4-rc5-15-g3ea7daa5d7fd Tested-on: linux 4.4 v2: update man about layouts and add more test cases (with reducing number of devices) as suggested by NeilBrown v4: cover internal bitmap mode as suggested by Zhilong Liu Signed-off-by: Azat Khuzhin <a3at.mail@xxxxxxxxx> Cc: NeilBrown <neilb@xxxxxxxx> Cc: Zhilong Liu <zlliu@xxxxxxxx> Link: https://www.spinics.net/lists/raid/msg60522.html --- mdadm.8.in | 3 ++- tests/02r10reshape | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 68 insertions(+), 1 deletion(-) create mode 100644 tests/02r10reshape diff --git a/mdadm.8.in b/mdadm.8.in index f0fd1fc..0a1907c 100644 --- a/mdadm.8.in +++ b/mdadm.8.in @@ -123,7 +123,8 @@ missing, spare, or failed drives, so there is nothing to monitor. Grow (or shrink) an array, or otherwise reshape it in some way. Currently supported growth options including changing the active size of component devices and changing the number of active devices in -Linear and RAID levels 0/1/4/5/6, +Linear and RAID levels 0/1/4/5/6 and 10 (but only with 'offset' or 'near' +layout), changing the RAID level between 0, 1, 5, and 6, and between 0 and 10, changing the chunk size and layout for RAID 0,4,5,6,10 as well as adding or removing a write-intent bitmap and changing the array's consistency policy. diff --git a/tests/02r10reshape b/tests/02r10reshape new file mode 100644 index 0000000..15bf879 --- /dev/null +++ b/tests/02r10reshape @@ -0,0 +1,66 @@ + +# create a 4-disk raid10 array, make it 8-disk array and than shrink it back +# +# This SHOULD fail: +# - before mdadm 3.3 and linux 3.5 +# - with metadata v0.90 +# +# This also fails: +# - with metadata 1.0 with "mdadm: Insufficient head-space for reshape on /dev/loop1" error +# - and external bitmap mode + +function get_component_size() { cat /sys/block/$1/md/component_size; } + +function raid10_reshape() +{ + local layout=$1 metadata=$2 bitmap=$3 + shift 3 + + local m=2 cm=1 + + echo "Checking layout=$layout/metadata=$metadata" + + # 4 disks + mdadm -CR $md0 --bitmap $bitmap --metadata $metadata --level raid10 --layout $layout --raid-disks 4 $dev1 $dev2 $dev3 $dev4 + check wait + check state UUUU + check raid10 + testdev $md0 $m $mdsize1 $[512*cm] + + # growing array to 8 disks + mdadm $md0 --add $dev8 $dev9 $dev10 $dev11 + mdadm $md0 --grow --raid-devices 8 + check wait + check state UUUUUUUU + check raid10 + testdev $md0 $m $[mdsize1*2] $[512*cm] + + # reducing array to 4 disks again + dsize=$(get_component_size md0) + mdadm $md0 --grow --array-size $[dsize*2] + mdadm $md0 --grow --raid-devices 4 + check wait + mdadm $md0 --remove $dev8 $dev9 $dev10 $dev11 + check state UUUU + check raid10 + testdev $md0 $m $mdsize1 $[512*cm] +} + +function run_test() +{ + "$@" + mdadm -S $md0 +} +function main() +{ + local layout metadata bitmap + + for layout in n2 o2; do + for metadata in 1.1 1.2; do + for bitmap in none internal; do + run_test raid10_reshape $layout $metadata $bitmap + done + done + done +} +main "$@" -- 2.16.1 -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
