From: Zhilong Liu <zlliu@suse.com>
To: jsorensen@fb.com
Cc: linux-raid@vger.kernel.org, Zhilong Liu <zlliu@suse.com>
Subject: [PATCH 07/13] mdadm/test: redraft the 00raid10 test case
Date: Fri, 1 Dec 2017 17:48:08 +0800 [thread overview]
Message-ID: <1512121694-18168-8-git-send-email-zlliu@suse.com> (raw)
In-Reply-To: <1512121694-18168-1-git-send-email-zlliu@suse.com>
make it cover different bitmap, metadata and
"near, far, offset" layouts.
Signed-off-by: Zhilong Liu <zlliu@suse.com>
---
tests/00raid10 | 41 +++++++++++++++++++++++++++++------------
1 file changed, 29 insertions(+), 12 deletions(-)
diff --git a/tests/00raid10 b/tests/00raid10
index 796b970..9929ee7 100644
--- a/tests/00raid10
+++ b/tests/00raid10
@@ -1,18 +1,35 @@
# Create some raid10 arrays, all with 6 devices and one spare
devs="$dev0 $dev1 $dev2 $dev3 $dev4 $dev5 $dev6"
+bmf=$targetdir/bm
-for lo in n2 n3 f2 f3
+for bm in $bmf internal none
do
- cm=1
- case $lo in
- f2 ) m=3 cm=2;;
- f3 ) m=2 cm=3;;
- n2 ) m=3;;
- n3 ) m=2;;
- esac
- mdadm --create --run --level=raid10 --layout $lo --raid-disks 6 -x 1 $md0 $devs
- check resync ; check raid10
- testdev $md0 $m $mdsize1 $[512*cm]
- mdadm -S $md0
+ for metadata in 0.90 1.1 1.2 default
+ do
+ for lo in n2 n3 f2 f3 o2 o3
+ do
+ cm=1
+ case $lo in
+ f2 ) m=3 cm=2;;
+ f3 ) m=2 cm=3;;
+ n2 ) m=3;;
+ n3 ) m=2;;
+ o3 ) m=2;;
+ o2 ) m=3;;
+ esac
+ [ "$bm" == "$bmf" -a -f $bmf ] && rm $bmf
+ mdadm --create --run --level=raid10 -e $metadata -b $bm --layout $lo --raid-disks 6 -x 1 $md0 $devs
+ check resync
+ check raid10
+ check wait
+ check state UUUUUU
+ check spares 1
+ testdev $md0 $m $mdsize1 $[512*cm]
+ mdadm -S $md0
+ done
+ done
done
+[ -f $bmf ] && rm $bmf
+
+exit 0
--
1.8.5.6
next prev parent reply other threads:[~2017-12-01 9:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 9:48 [RFC PATCH 00/13] mdadm/test: Basic improvement for some cases Zhilong Liu
2017-12-01 9:48 ` [PATCH 01/13] mdadm/manpage: raid10 doesn't support resize 'far' arrays Zhilong Liu
2017-12-01 9:48 ` [PATCH 02/13] mdadm/test: did basic improvement for 00names Zhilong Liu
2017-12-01 9:48 ` [PATCH 03/13] mdadm/test: redraft the 00raid1 test case Zhilong Liu
2017-12-01 9:48 ` [PATCH 04/13] mdadm/test: redraft 00raid4 " Zhilong Liu
2017-12-01 9:48 ` [PATCH 05/13] mdadm/test: redraft the 00raid5 " Zhilong Liu
2017-12-01 9:48 ` [PATCH 06/13] mdadm/test: redraft the 00raid6 " Zhilong Liu
2017-12-01 9:48 ` Zhilong Liu [this message]
2017-12-01 9:48 ` [PATCH 08/13] mdadm/test: redraft 02r5grow and rename it as 02r5grow-resize Zhilong Liu
2017-12-01 9:48 ` [PATCH 09/13] mdadm/test: redraft 02r6grow and rename it as 02r6grow-resize Zhilong Liu
2017-12-01 9:48 ` [PATCH 10/13] mdadm/test: add new test 02r10grow-resize Zhilong Liu
2017-12-01 9:48 ` [PATCH 11/13] mdadm/test: did basic improvement for 05r1-internalbitmap Zhilong Liu
2017-12-01 9:48 ` [PATCH 12/13] mdadm/test: did basic improvement for 05r1-n3-bitmapfile Zhilong Liu
2017-12-01 9:48 ` [PATCH 13/13] mdadm/test: Change check nosync as check recovery in 05r1-re-add-nosuper Zhilong Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1512121694-18168-8-git-send-email-zlliu@suse.com \
--to=zlliu@suse.com \
--cc=jsorensen@fb.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).