From: Eryu Guan <guaneryu@gmail.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] fstest: btrfs/197: test for alien devices
Date: Fri, 18 Oct 2019 17:13:44 +0800 [thread overview]
Message-ID: <20191018091344.GL2622@desktop> (raw)
In-Reply-To: <20191007094101.784-2-anand.jain@oracle.com>
On Mon, Oct 07, 2019 at 05:41:01PM +0800, Anand Jain wrote:
> Test if btrfs.ko sucessfully identifies and reports the missing device,
> if the missed device contians no btrfs magic string.
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> tests/btrfs/197 | 79 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/197.out | 25 +++++++++++++++++
> tests/btrfs/group | 1 +
> 3 files changed, 105 insertions(+)
> create mode 100755 tests/btrfs/197
> create mode 100644 tests/btrfs/197.out
>
> diff --git a/tests/btrfs/197 b/tests/btrfs/197
> new file mode 100755
> index 000000000000..82e1a299ca43
> --- /dev/null
> +++ b/tests/btrfs/197
> @@ -0,0 +1,79 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2019 Oracle. All Rights Reserved.
> +#
> +# FS QA Test 197
> +#
> +# Test stale and alien device in the fs devices list.
> +# Similar to the testcase btrfs/196 except that here the alien device no more
> +# contains the btrfs superblock.
> +#
> +seq=`basename $0`
> +seqres=$RESULT_DIR/$seq
> +echo "QA output created by $seq"
> +
> +here=`pwd`
> +tmp=/tmp/$$
> +status=1 # failure is the default!
> +trap "_cleanup; exit \$status" 0 1 2 3 15
> +
> +_cleanup()
> +{
> + cd /
> + rm -f $tmp.*
> +}
> +
> +# get standard environment, filters and checks
> +. ./common/rc
> +. ./common/filter
> +. ./common/filter.btrfs
> +
> +# remove previous $seqres.full before test
> +rm -f $seqres.full
> +
> +# real QA test starts here
> +
> +# Modify as appropriate.
> +_supported_fs generic
> +_supported_os Linux
> +_require_command "$WIPEFS_PROG" wipefs
> +_require_scratch
> +_require_scratch_dev_pool 4
> +
> +workout()
> +{
> + raid=$1
> + device_nr=$2
> +
> + echo $raid
> + _scratch_dev_pool_get $device_nr
> +
> + _scratch_pool_mkfs "-d$raid -m$raid" >> $seqres.full 2>&1 || \
> + _fail "mkfs failed"
> +
> + # Make device_1 an alien btrfs device for the raid created above by
> + # adding it to the $TEST_DIR
Stale comments above.
Otherwise looks fine to me.
> +
> + # don't test with the first device as auto fs check (_check_scratch_fs)
> + # picks the first device
> + device_1=$(echo $SCRATCH_DEV_POOL | awk '{print $2}')
> + $WIPEFS_PROG -a $device_1 >> $seqres.full 2>&1
If creating a new btrfs works for btrfs/196, I wonder if we could merge
the two tests into one test, firstly create a new fs & degraded mount,
then wipefs & degraded mount.
Thanks,
Eryu
> +
> + device_2=$(echo $SCRATCH_DEV_POOL | awk '{print $1}')
> + _mount -o degraded $device_2 $SCRATCH_MNT
> + # Check if missing device is reported as in the 196.out
> + $BTRFS_UTIL_PROG filesystem show -m $SCRATCH_MNT | \
> + _filter_btrfs_filesystem_show
> +
> + _scratch_unmount
> + _scratch_dev_pool_put
> +}
> +
> +workout "raid1" "2"
> +workout "raid5" "3"
> +workout "raid6" "4"
> +workout "raid10" "4"
> +
> +# success, all done
> +status=0
> +exit
> diff --git a/tests/btrfs/197.out b/tests/btrfs/197.out
> new file mode 100644
> index 000000000000..79237b854b5a
> --- /dev/null
> +++ b/tests/btrfs/197.out
> @@ -0,0 +1,25 @@
> +QA output created by 197
> +raid1
> +Label: none uuid: <UUID>
> + Total devices <NUM> FS bytes used <SIZE>
> + devid <DEVID> size <SIZE> used <SIZE> path SCRATCH_DEV
> + *** Some devices missing
> +
> +raid5
> +Label: none uuid: <UUID>
> + Total devices <NUM> FS bytes used <SIZE>
> + devid <DEVID> size <SIZE> used <SIZE> path SCRATCH_DEV
> + *** Some devices missing
> +
> +raid6
> +Label: none uuid: <UUID>
> + Total devices <NUM> FS bytes used <SIZE>
> + devid <DEVID> size <SIZE> used <SIZE> path SCRATCH_DEV
> + *** Some devices missing
> +
> +raid10
> +Label: none uuid: <UUID>
> + Total devices <NUM> FS bytes used <SIZE>
> + devid <DEVID> size <SIZE> used <SIZE> path SCRATCH_DEV
> + *** Some devices missing
> +
> diff --git a/tests/btrfs/group b/tests/btrfs/group
> index c86ea2516397..f2eac5c20712 100644
> --- a/tests/btrfs/group
> +++ b/tests/btrfs/group
> @@ -199,3 +199,4 @@
> 194 auto volume
> 195 auto volume
> 196 auto quick volume
> +197 auto quick volume
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2019-10-18 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 9:41 [PATCH 1/2] fstest: btrfs/196: test for alien btrfs-devices Anand Jain
2019-10-07 9:41 ` [PATCH 2/2] fstest: btrfs/197: test for alien devices Anand Jain
2019-10-18 9:13 ` Eryu Guan [this message]
2019-10-22 9:23 ` Anand Jain
2019-10-18 9:10 ` [PATCH 1/2] fstest: btrfs/196: test for alien btrfs-devices Eryu Guan
2019-10-22 9:23 ` Anand Jain
2019-10-22 9:24 ` [PATCH v2 1/2] fstest: btrfs/197: " Anand Jain
2019-10-22 9:24 ` [PATCH v2 2/2] fstest: btrfs/198: test for alien devices Anand Jain
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=20191018091344.GL2622@desktop \
--to=guaneryu@gmail.com \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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 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.