From: "Darrick J. Wong" <djwong@kernel.org>
To: Naohiro Aota <naohiro.aota@wdc.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 3/3] fstests: generic: add checks for zoned block device
Date: Tue, 17 Aug 2021 17:01:09 -0700 [thread overview]
Message-ID: <20210818000109.GB12612@magnolia> (raw)
In-Reply-To: <20210816113510.911606-4-naohiro.aota@wdc.com>
On Mon, Aug 16, 2021 at 08:35:10PM +0900, Naohiro Aota wrote:
> Modify generic tests to require non-zoned block device
>
> generic/108 is disabled on zoned block device because the LVM device not
> always aligned to the zone boundary.
>
> generic/471 is disabled because we cannot enable NoCoW on zoned btrfs.
>
> generic/570 is disabled because swap file which require nocow is not usable
> on zoned btrfs.
>
> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
I'm surprised that only three generic tests needed the annotation, but
the logic makes sense, so
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> tests/generic/108 | 2 ++
> tests/generic/471 | 2 ++
> tests/generic/570 | 2 ++
> 3 files changed, 6 insertions(+)
>
> diff --git a/tests/generic/108 b/tests/generic/108
> index b7797e8fac2b..6e1ea5b9d20a 100755
> --- a/tests/generic/108
> +++ b/tests/generic/108
> @@ -36,6 +36,8 @@ _require_scratch_nocheck
> _require_block_device $SCRATCH_DEV
> _require_scsi_debug
> _require_command "$LVM_PROG" lvm
> +# We cannot ensure the Logical Volume is aligned to the zone boundary
> +_require_non_zoned_device $SCRATCH_DEV
>
> lvname=lv_$seq
> vgname=vg_$seq
> diff --git a/tests/generic/471 b/tests/generic/471
> index dab06f3a315c..fbd0b12a9e3a 100755
> --- a/tests/generic/471
> +++ b/tests/generic/471
> @@ -37,6 +37,8 @@ mkdir $testdir
> # all filesystems, use a NOCOW file on btrfs.
> if [ $FSTYP == "btrfs" ]; then
> _require_chattr C
> + # Zoned btrfs does not support NOCOW
> + _require_non_zoned_device $TEST_DEV
> touch $testdir/f1
> $CHATTR_PROG +C $testdir/f1
> fi
> diff --git a/tests/generic/570 b/tests/generic/570
> index 7d03acfe3c44..126b222d10d2 100755
> --- a/tests/generic/570
> +++ b/tests/generic/570
> @@ -25,6 +25,8 @@ _supported_fs generic
> _require_test_program swapon
> _require_scratch_nocheck
> _require_block_device $SCRATCH_DEV
> +# We cannot create swap on a zoned device because it can cause random write IOs
> +_require_non_zoned_device "$SCRATCH_DEV"
> test -e /dev/snapshot && _notrun "userspace hibernation to swap is enabled"
>
> $MKSWAP_PROG "$SCRATCH_DEV" >> $seqres.full
> --
> 2.32.0
>
prev parent reply other threads:[~2021-08-18 0:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 11:35 [PATCH v3 0/3] fstests: add checks for testing zoned btrfs Naohiro Aota
2021-08-16 11:35 ` [PATCH v3 1/3] common: add zoned block device checks Naohiro Aota
2021-08-17 23:59 ` Darrick J. Wong
2021-08-18 2:51 ` Naohiro Aota
2021-08-16 11:35 ` [PATCH v3 2/3] fstests: btrfs: add checks for zoned block device Naohiro Aota
2021-08-16 11:35 ` [PATCH v3 3/3] fstests: generic: " Naohiro Aota
2021-08-18 0:01 ` Darrick J. Wong [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=20210818000109.GB12612@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.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).