From: Eryu Guan <guaneryu@gmail.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Enable btrfs/003
Date: Sat, 30 Mar 2019 17:34:41 +0800 [thread overview]
Message-ID: <20190330093441.GZ2824@desktop> (raw)
In-Reply-To: <20190319105851.9280-1-nborisov@suse.com>
On Tue, Mar 19, 2019 at 12:58:51PM +0200, Nikolay Borisov wrote:
> For a long time this test has been failing on all kinds of VM configuration,
> which are using virtio_blk devices. This is due to the fact that scsi
> devices are deletable and virtio_blk are not. However, this only prevents
> device replace case to run and has no negative effect on the other
> useful test cases.
>
> Re-enable btrfs/003 to run by making _require_deletable_scratch_dev_pool
> private to the test case and modifying it to return success (0) or
> failure (1) if devices are not deletable. Further modify the replace
> test case to check the return value of this function and skip it if
> devices are not deletable.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> ---
> common/rc | 12 ------------
> tests/btrfs/003 | 19 ++++++++++++++++++-
> 2 files changed, 18 insertions(+), 13 deletions(-)
>
> diff --git a/common/rc b/common/rc
> index 1c42515ff0ea..5693ba3cad18 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -2961,18 +2961,6 @@ _require_scratch_dev_pool_equal_size()
> done
> }
>
> -# We will check if the device is deletable
> -_require_deletable_scratch_dev_pool()
> -{
> - local i
> - local x
> - for i in $SCRATCH_DEV_POOL; do
> - x=`echo $i | cut -d"/" -f 3`
> - if [ ! -f /sys/class/block/${x}/device/delete ]; then
> - _notrun "$i is a device which is not deletable"
> - fi
> - done
> -}
>
> # Check that fio is present, and it is able to execute given jobfile
> _require_fio()
> diff --git a/tests/btrfs/003 b/tests/btrfs/003
> index 938030ef4c65..2aeb9fe6325a 100755
> --- a/tests/btrfs/003
> +++ b/tests/btrfs/003
> @@ -17,6 +17,21 @@ dev_removed=0
> removed_dev_htl=""
> trap "_cleanup; exit \$status" 0 1 2 3 15
>
> +# Check if all scratch dev pools are deletable
> +_require_deletable_scratch_dev_pool()
Then it's not a _require rule anymore, maybe we could just rename it to
something like "deletable_scratch_dev_pool"? Also remove the leading "_"
if it becomes a private function.
Thanks,
Eryu
> +{
> + local i
> + local x
> + for i in $SCRATCH_DEV_POOL; do
> + x=`echo $i | cut -d"/" -f 3`
> + if [ ! -f /sys/class/block/${x}/device/delete ]; then
> + return 1
> + fi
> + done
> +
> + return 0
> +}
> +
> _cleanup()
> {
> cd /
> @@ -35,7 +50,6 @@ _supported_fs btrfs
> _supported_os Linux
> _require_scratch
> _require_scratch_dev_pool 4
> -_require_deletable_scratch_dev_pool
> _require_command "$WIPEFS_PROG" wipefs
>
> rm -f $seqres.full
> @@ -111,6 +125,9 @@ _test_replace()
> local ds
> local d
>
> + # If scratch devs are not deletable skip this test
> + if ! _require_deletable_scratch_dev_pool; then return 0; fi
> +
> # exclude the first and the last disk in the disk pool
> n=$(($n-1))
> ds=${devs[@]:1:$(($n-1))}
> --
> 2.7.4
>
prev parent reply other threads:[~2019-03-30 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 10:58 [PATCH] btrfs: Enable btrfs/003 Nikolay Borisov
2019-03-26 15:03 ` Nikolay Borisov
2019-03-30 9:34 ` Eryu Guan [this message]
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=20190330093441.GZ2824@desktop \
--to=guaneryu@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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).