public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: bingjingc <bingjingc@synology.com>
Cc: linux-block@vger.kernel.org, cccheng@synology.com,
	linux-raid@vger.kernel.org
Subject: Re: [PATCH blktests 1/9] blktests: add hepler functions for new md tests
Date: Wed, 6 Jun 2018 10:44:02 +0200	[thread overview]
Message-ID: <20180606084402.vmx4qi42bmj5tmb4@linux-x5ow.site> (raw)
In-Reply-To: <1528272400-7128-1-git-send-email-bingjingc@synology.com>

On Wed, Jun 06, 2018 at 04:06:40PM +0800, bingjingc wrote:
> We'd like to leverage this test framework for testing linux raid
> software. There are several resync tasks in md/raid. For this commit,
> we are trying to add creation resync and basic recovery tests for
> every raid type.
> 
> RAID is different from other block devices. It requires several
> raid devices and hotspare devices for being assembled, disambled,
> expended or recovered in the runtime. So we don't test devices
> iteratively in TEST_DEVS list. We define RAID_DEVS and
> RAID_SPARE_DEVS lists for providing block devices instead.
> 
> We want to test the software not devices. We also provide a
> LIMIT_DEV_SIZE option for limiting the tested array size by limiting
> used space for each block device.
> 
> [Getting Started]
> 
> Additional dependencies are also minimal:
> - mdadm
> - cmp
> 
> And please provide a file named config:
> RAID_DEVS=(/dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4)
> RAID_SPARE_DEVS=(/dev/loop100 /dev/loop101)
> LIMIT_DEV_SIZE=20480 # optional
> 
> And as root, you can run the md set of tests by typing
> ./check md
> 
> For someone who don't want to run md tests, they just keep RAID_DEVS
> and RAID_SPARE_DEVS not assigned, all md tests will be skipped.

While I'm very much in support for the idea, please be aware that md
has an own test suite by itself and please Cc the md mailing list as
well.

Thanks,
	Johannes
-- 
Johannes Thumshirn                                          Storage
jthumshirn@suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg
GF: Felix Imend�rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N�rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

  reply	other threads:[~2018-06-06  8:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06  8:06 [PATCH blktests 1/9] blktests: add hepler functions for new md tests bingjingc
2018-06-06  8:44 ` Johannes Thumshirn [this message]
2018-06-06 14:29   ` Jens Axboe
2018-06-06 14:33     ` Johannes Thumshirn
2018-06-07  2:45       ` bingjingc
2018-06-07  6:55         ` Johannes Thumshirn
2018-06-07 12:59           ` Jens Axboe
2018-06-08 14:50         ` Wols Lists

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=20180606084402.vmx4qi42bmj5tmb4@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=bingjingc@synology.com \
    --cc=cccheng@synology.com \
    --cc=linux-block@vger.kernel.org \
    --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