From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Zhao Lei <zhaolei@cn.fujitsu.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 3/3] btrfs-progs: tests: Introduce misc-tests/008-leaf-accross-stripes
Date: Wed, 9 Sep 2015 09:46:00 +0800 [thread overview]
Message-ID: <55EF8F58.4070407@cn.fujitsu.com> (raw)
In-Reply-To: <87244a2006270f7f8a32680ce8ba7656e277a4bd.1441373012.git.zhaolei@cn.fujitsu.com>
Zhao Lei wrote on 2015/09/04 21:23 +0800:
> To check is btrfs-convert create bad filesystem with
> leaf accross stripes.
>
> It is happened in progs version <=v4.1.2, and fixed by patch titled:
> btrfs: convert: Avoid allocating metadata extent crossing stripe boundary
> which was merged in v4.2.
>
> Notice thar this testcase can not report error in old version of
> btrfs-progs, because "btrfs check" can't check this type of error
> in those version, but we have another testcase in fsck-tests, to
> check is "btrfs check" support this check.
>
> So, use above 2 testcase together can check out leaf-accross-stripes
> bug in all version.
>
> Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> ---
> tests/misc-tests/008-leaf-accross-stripes/test.sh | 24 +++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
> create mode 100755 tests/misc-tests/008-leaf-accross-stripes/test.sh
>
> diff --git a/tests/misc-tests/008-leaf-accross-stripes/test.sh b/tests/misc-tests/008-leaf-accross-stripes/test.sh
> new file mode 100755
> index 0000000..4801dce
> --- /dev/null
> +++ b/tests/misc-tests/008-leaf-accross-stripes/test.sh
> @@ -0,0 +1,24 @@
> +#!/bin/bash
> +# test btrfs subvolume run normally with more than one subvolume
> +#
> +# - btrfs subvolume must not loop indefinetelly
> +# - btrfs subvolume return 0 in normal case
> +
> +source $TOP/tests/common
> +
> +check_prereq btrfs-convert
> +check_prereq btrfs
> +
> +# In my test, it happened in 514M~560M, 737M~769M, 929M~917M,
> +# and HAVE_ERROR=((size + 1) / 2) % 2 if size >= 970
> +#
> +SIZE_FROM=514
> +SIZE_END=560
> +A_PRIME_NUM=17
> +for ((size = SIZE_FROM; size <= SIZE_END; size += A_PRIME_NUM)); do
> + run_check truncate -s "$size"M "$IMAGE"
> + run_check mkfs.ext4 -F "$IMAGE"
> + run_check $TOP/btrfs-convert "$IMAGE"
> + $TOP/btrfs check "$IMAGE" 2>&1 | grep "crossing stripe boundary" &&
> + _fail "leaf accross stripes in btrfs-convert"
> +done
>
Maybe I'm wrong, but even with your script, I still can't reproduce the bug.
After some search in git log, I found that, from 4.1 btrfs-convert won't
allow mixed block group since the following commit:
commit c9b73b702be71bbc1a3a815a745e6e4e57eadffc
Author: David Sterba <dsterba@suse.cz>
Date: Mon Mar 23 19:31:31 2015 +0100
btrfs-progs: convert: allow to set filesystem features
So the new test may not be necessary and won't reproduce the bug.
Thanks,
Qu
next prev parent reply other threads:[~2015-09-09 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 13:23 [PATCH 1/3] btrfs-progs: tests: Move extract_image out of check_all_images for common use Zhao Lei
2015-09-04 13:23 ` [PATCH 2/3] btrfs-progs: tests: Introduce fsck-tests/018-leaf-accross-stripes Zhao Lei
2015-09-04 13:23 ` [PATCH 3/3] btrfs-progs: tests: Introduce misc-tests/008-leaf-accross-stripes Zhao Lei
2015-09-09 1:46 ` Qu Wenruo [this message]
2015-09-09 9:09 ` Zhao Lei
2015-09-22 7:14 ` [PATCH 1/3] btrfs-progs: tests: Move extract_image out of check_all_images for common use David Sterba
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=55EF8F58.4070407@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zhaolei@cn.fujitsu.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