From: Rich Johnston <rjohnston@sgi.com>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: <xfs@oss.sgi.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH V2] xfstest: add a test for btrfs device replace operation
Date: Wed, 14 Aug 2013 17:18:36 -0500 [thread overview]
Message-ID: <520C023C.5050307@sgi.com> (raw)
In-Reply-To: <1375285960-4039-1-git-send-email-sbehrens@giantdisaster.de>
On 07/31/2013 10:52 AM, Stefan Behrens wrote:
> This test performs btrfs device replace tests with all possible profiles
> (single/dup/mixed/raid0/raid1/raid10), one round with the '-r' option
> to 'btrfs replace start' and one round without this option. The
> cancelation is tested only once and with the dup/single profile for
> metadata/data.
>
> This test takes 181 seconds on my SSD equiped test box and 237s on
> spinning disks. Almost all the time is spent when the filesystem is
> populated with test data. The replace operation itself takes less than
> a second for all the tests, except for the test that is marked as
> 'thorough' which will run for about 8 seconds on my test box.
>
> The amount of tests done depends on the number of devices in the
> SCRATCH_DEV_POOL. For full test coverage, at least 5 devices should
> be available (e.g. 5 partitions). With less than 2 entries in
> SCRATCH_DEV_POOL, the test is not executed.
>
> The source and target devices for the replace operation are arbitrarily
> chosen out of SCRATCH_DEV_POOl. Since the target device mustn't be
> smaller than the source device, the requirement for this test is that
> all devices have _exactly_ the same size. If this is not the case, the
> test terminates with _notrun.
>
> To check the filesystems after replacing a device, a scrub run is
> performed, a btrfsck run, and finally the filesystem is remounted.
>
> This commit depends on my other commit:
> "xfstest: don't remove the two first devices from SCRATCH_DEV_POOL"
>
> Signed-off-by: Stefan Behrens <sbehrens@giantdisaster.de>
> ---
> V1 -> V2:
> Major reworking in order to address all the comments from Eric Sandeen's
> review.
>
> common/config | 1 +
> tests/btrfs/317 | 273 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/317.out | 3 +
> tests/btrfs/group | 1 +
> 4 files changed, 278 insertions(+)
>
Hey Stefan,
Thanks for submitting this patch. This patch had not been reviewed
before I pulled in commit aab6d4e
"xfstests: renumber existing btrfs tests to start with 1"
Will you please rebase this off the current xfstests tree.
Thanks
--Rich
WARNING: multiple messages have this Message-ID (diff)
From: Rich Johnston <rjohnston@sgi.com>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH V2] xfstest: add a test for btrfs device replace operation
Date: Wed, 14 Aug 2013 17:18:36 -0500 [thread overview]
Message-ID: <520C023C.5050307@sgi.com> (raw)
In-Reply-To: <1375285960-4039-1-git-send-email-sbehrens@giantdisaster.de>
On 07/31/2013 10:52 AM, Stefan Behrens wrote:
> This test performs btrfs device replace tests with all possible profiles
> (single/dup/mixed/raid0/raid1/raid10), one round with the '-r' option
> to 'btrfs replace start' and one round without this option. The
> cancelation is tested only once and with the dup/single profile for
> metadata/data.
>
> This test takes 181 seconds on my SSD equiped test box and 237s on
> spinning disks. Almost all the time is spent when the filesystem is
> populated with test data. The replace operation itself takes less than
> a second for all the tests, except for the test that is marked as
> 'thorough' which will run for about 8 seconds on my test box.
>
> The amount of tests done depends on the number of devices in the
> SCRATCH_DEV_POOL. For full test coverage, at least 5 devices should
> be available (e.g. 5 partitions). With less than 2 entries in
> SCRATCH_DEV_POOL, the test is not executed.
>
> The source and target devices for the replace operation are arbitrarily
> chosen out of SCRATCH_DEV_POOl. Since the target device mustn't be
> smaller than the source device, the requirement for this test is that
> all devices have _exactly_ the same size. If this is not the case, the
> test terminates with _notrun.
>
> To check the filesystems after replacing a device, a scrub run is
> performed, a btrfsck run, and finally the filesystem is remounted.
>
> This commit depends on my other commit:
> "xfstest: don't remove the two first devices from SCRATCH_DEV_POOL"
>
> Signed-off-by: Stefan Behrens <sbehrens@giantdisaster.de>
> ---
> V1 -> V2:
> Major reworking in order to address all the comments from Eric Sandeen's
> review.
>
> common/config | 1 +
> tests/btrfs/317 | 273 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/317.out | 3 +
> tests/btrfs/group | 1 +
> 4 files changed, 278 insertions(+)
>
Hey Stefan,
Thanks for submitting this patch. This patch had not been reviewed
before I pulled in commit aab6d4e
"xfstests: renumber existing btrfs tests to start with 1"
Will you please rebase this off the current xfstests tree.
Thanks
--Rich
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-14 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 15:52 [PATCH V2] xfstest: add a test for btrfs device replace operation Stefan Behrens
2013-07-31 15:52 ` Stefan Behrens
2013-08-14 22:18 ` Rich Johnston [this message]
2013-08-14 22:18 ` Rich Johnston
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=520C023C.5050307@sgi.com \
--to=rjohnston@sgi.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.