From: Zhilong Liu <zlliu@suse.com>
To: Xiao Ni <xni@redhat.com>, linux-raid@vger.kernel.org
Cc: jes.sorensen@gmail.com
Subject: Re: [PATCH -v2 1/1] mdadm/test: Add one test case for raid5 reshape
Date: Tue, 18 Jul 2017 12:37:32 +0800 [thread overview]
Message-ID: <3d22eddd-79cc-4877-8c0d-497ea80e829b@suse.com> (raw)
In-Reply-To: <1500283627-15195-1-git-send-email-xni@redhat.com>
On 07/17/2017 05:27 PM, Xiao Ni wrote:
> This case trys to allow raid5 reshape to use backwards direction.
> It changes chunksize after reshape and stop the raid. Then start
> the raid again.
>
> Signed-off-by: Xiao Ni <xni@redhat.com>
> ---
> tests/02r5grow | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/tests/02r5grow b/tests/02r5grow
> index 386e82e..64c5599 100644
> --- a/tests/02r5grow
> +++ b/tests/02r5grow
> @@ -34,3 +34,16 @@ check nosync
> sh tests/testdev $md0 3 $[size/2] 128
>
> mdadm -S $md0
> +
> +# create a raid5 array and change the chunk
> +mdadm -CR $md0 --level raid5 --metadata=1.1 --chunk=32 --raid-disks 3 --size $[size/2] $dev1 $dev2 $dev3
> +check wait
> +check state UUU
> +
Hi,
Just my opinion, it should check the chunk-size properly if you
wanna test 'chunk'.
Maybe can do following three things in a function.
From sysfs:
new_size=$(cat /sys/block/md0/md/chunk_size)
if [ "$(expr 32 \* 1024)" -eq "$new_size" ]; then
...
fi
From procfs:
# cat /proc/mdstat | awk -F',' '/chunk/{print $2}'
32k chunk
From superblock:
mdadm -D /dev/md0 | grep "Chunk Size"
It's important for testing based on expected environment.
> +mdadm $md0 --grow --chunk=64
> +check reshape
> +check wait
Here too.
> +
> +mdadm -S $md0
> +mdadm -As
> +check state UUU
Also here.
Thanks,
-Zhilong
next prev parent reply other threads:[~2017-07-18 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 9:27 [PATCH -v2 1/1] mdadm/test: Add one test case for raid5 reshape Xiao Ni
2017-07-18 4:37 ` Zhilong Liu [this message]
2017-07-18 8:43 ` Xiao Ni
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=3d22eddd-79cc-4877-8c0d-497ea80e829b@suse.com \
--to=zlliu@suse.com \
--cc=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=xni@redhat.com \
/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