linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
	xfs@oss.sgi.com, anand.jain@oracle.com
Subject: Re: [PATCH 3/3] xfstests: fix wrong number of the required devices and add independent device check for case 265
Date: Fri, 24 Aug 2012 14:18:04 +1000	[thread overview]
Message-ID: <20120824041804.GB19235@dastard> (raw)
In-Reply-To: <5036F1FB.80205@cn.fujitsu.com>

On Fri, Aug 24, 2012 at 11:16:11AM +0800, Miao Xie wrote:
> Case 265 need 4 devices to test RAID10, so we need 4 or more devices not 2.
> and it is better that these 4 devices are independent devices, especially
> the 2nd last one, so we add independent device check to check the devices
> in SCRATCH_DEV_POOL.

I don't see any reason for requiring the devices to be independent.
You're basically checking if the devices are on an MD device, which
isn't really a check for indpendent devices. e.g. my 4 devices could
be loopback devices with files all the in the same filesystem, or on
a VM using images at that are all hosted on the same device, or LVM
volumes on top of a single MD device, hardware lun, etc. They are
most certainly not independent, but your test won't pick up any of
them.

Hence the test does not require the devices to be independent to run
correctly.  Sure, the test will run faster if each device is on an
independent spindle, but it's not a requirement for test success or
failure....

> diff --git a/common.rc b/common.rc
> index 602513a..ede25fe 100644
> --- a/common.rc
> +++ b/common.rc
> @@ -1699,12 +1699,14 @@ _require_scratch_dev_pool()
>  		_notrun "this test requires a valid \$SCRATCH_DEV_POOL"
>  	fi
>  
> -	# btrfs test case needs 2 or more scratch_dev_pool; other FS not sure
> +	# btrfs test case needs 4 or more scratch_dev_pool; other FS not sure
>  	# so fail it
> +	# common.config has moved the first device to SCRATCH_DEV, so
> +	# SCRATCH_DEV_POOL should have 3 or more disks.
>  	case $FSTYP in
>  	btrfs)
> -		if [ "`echo $SCRATCH_DEV_POOL|wc -w`" -lt 2 ]; then
> -			_notrun "btrfs and this test needs 2 or more disks in SCRATCH_DEV_POOL"
> +		if [ "`echo $SCRATCH_DEV_POOL|wc -w`" -lt 3 ]; then
> +			_notrun "btrfs and this test needs 4 or more disks in SCRATCH_DEV_POOL"
>  		fi
>  	;;
>  	*)

Rather than changing this every time a new number of disks is
required, change it so that the number of devices required by the
test is passed as a parameter to _require_scratch_dev_pool.

Cheers,

Dave.

-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2012-08-24  4:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24  3:16 [PATCH 3/3] xfstests: fix wrong number of the required devices and add independent device check for case 265 Miao Xie
2012-08-24  4:18 ` Dave Chinner [this message]
2012-08-24  5:50   ` Miao Xie
2012-08-24  6:55     ` Miao Xie
2012-08-24  8:08 ` [PATCH V2 3/3] xfstests: fix wrong number of the required devices and wrong deletable device check method " Miao Xie

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=20120824041804.GB19235@dastard \
    --to=david@fromorbit.com \
    --cc=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miaox@cn.fujitsu.com \
    --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 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).