From: Eryu Guan <eguan@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: fstests@vger.kernel.org, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] fstests: fix _filter_mkfs regression on btrfs
Date: Fri, 27 Mar 2015 12:06:57 +0800 [thread overview]
Message-ID: <20150327040657.GA4810@dhcp-13-216.nay.redhat.com> (raw)
In-Reply-To: <551441CA.9050109@redhat.com>
On Thu, Mar 26, 2015 at 12:28:42PM -0500, Eric Sandeen wrote:
> commit:
>
> 5e8b9e6 btrfs: add regression test for remount with thread_pool resized
>
> did weird things to _filter_mkfs; aside from broken indentation,
> it also short-circuited the default non-xfs behavior, which was to
> emit a default block & inode size. And that was all because btrfs/082
> was using _filter_mkfs & not redirecting output away as per normal.
>
> Granted, it's not super clear that _filter_mkfs serves this rather
> unique purpose, but anyway...
>
> And, while having this default seems to be of questionable value,
> not emitting *anything* led to this on btrfs:
>
> +./tests/generic/204: line 76: space / (isize + dbsize): division by 0 (error token is ")")
>
> because those variables don't get set for btrfs, thanks to the
> above commit.
>
> So take out the use of _filter_mkfs in btrfs/082, and take out the
> munging of _filter_mkfs which broke generic/204, and get things back
> to something semi-sane.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Tested by running btrfs/082 and generic/204 on btrfs and all worked fine
One minor issue below
> ---
>
>
> diff --git a/common/filter b/common/filter
> index 71ef2e2..05dbae6 100644
> --- a/common/filter
> +++ b/common/filter
> @@ -137,10 +137,6 @@ _filter_mkfs()
> case $FSTYP in
> xfs)
> ;;
> - btrfs)
> - sed -e "/Performing full device TRIM/d" \
> - -e "/Turning ON incompat feature/d"
> - return ;;
> *)
> cat - >/dev/null
> perl -e 'print STDERR "dbsize=4096\nisize=256\n"'
>
> diff --git a/tests/btrfs/082 b/tests/btrfs/082
> index dd3c87e..1324d27 100755
> --- a/tests/btrfs/082
> +++ b/tests/btrfs/082
> @@ -55,7 +55,7 @@ _supported_fs btrfs
> _supported_os Linux
> _require_scratch
>
> -_scratch_mkfs |& _filter_mkfs
> +_scratch_mkfs >>$seqres.full 2>&1
Should rm -f $seqres.full, or the file is growing forever.
But I think simply >/dev/null is fine too, the following _scratch_mount
could catch any mkfs error.
Anyway, with this fixed:
Reviewed-by: Eryu Guan <eguan@redhat.com>
>
> _scratch_mount "-o thread_pool=6"
> _scratch_mount "-o remount,thread_pool=10"
>
> diff --git a/tests/generic/204 b/tests/generic/204
> index d6bb094..13069d8 100755
> --- a/tests/generic/204
> +++ b/tests/generic/204
> @@ -60,6 +60,7 @@ _scratch_mkfs_sized $SIZE $dbsize 2> /dev/null \
> | _filter_mkfs 2> $tmp.mkfs > /dev/null
> _scratch_mount
>
> +# Source $tmp.mkfs to get geometry
> . $tmp.mkfs
>
> # fix the reserve block pool to a known size so that the enospc calculations
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-27 4:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 17:28 [PATCH] fstests: fix _filter_mkfs regression on btrfs Eric Sandeen
2015-03-27 4:06 ` Eryu Guan [this message]
2015-03-27 20:44 ` [PATCH V2] " Eric Sandeen
2015-03-28 12:28 ` Filipe David Manana
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=20150327040657.GA4810@dhcp-13-216.nay.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandeen@redhat.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).