From: Eric Sandeen <sandeen@sandeen.net>
To: linux-btrfs@vger.kernel.org
Cc: fstests@vger.kernel.org
Subject: Re: xfstests seems broken on btrfs with multi-dev TEST_DEV
Date: Wed, 24 Feb 2021 15:39:34 -0600 [thread overview]
Message-ID: <5e133067-ec0c-f2c6-7fb6-84620e26881e@sandeen.net> (raw)
In-Reply-To: <3e8f846d-e248-52a3-9863-d188f031401e@sandeen.net>
On 2/24/21 10:12 AM, Eric Sandeen wrote:
> Last week I was curious to just see how btrfs is faring with RAID5 in
> xfstests, so I set it up for a quick run with devices configured as:
Whoops this was supposed to cc: fstests, not fsdevel, sorry.
-Eric
> TEST_DEV=/dev/sdb1 # <--- this was a 3-disk "-d raid5" filesystem
> SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4 /dev/sdb5 /dev/sdb6"
>
> and fired off ./check -g auto
>
> Every test after btrfs/124 fails, because that test btrfs/124 does this:
>
> # un-scan the btrfs devices
> _btrfs_forget_or_module_reload
>
> and nothing re-scans devices after that, so every attempt to mount TEST_DEV
> will fail:
>
>> devid 2 uuid e42cd5b8-2de6-4c85-ae51-74b61172051e is missing"
>
> Other btrfs tests seeme to have the same problem.
>
> If xfstest coverage on multi-device btrfs volumes is desired, it might be
> a good idea for someone who understands the btrfs framework in xfstests
> to fix this.
>
> Thanks,
> -Eric
>
next prev parent reply other threads:[~2021-02-24 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 16:12 xfstests seems broken on btrfs with multi-dev TEST_DEV Eric Sandeen
2021-02-24 21:39 ` Eric Sandeen [this message]
2021-02-25 1:16 ` Anand Jain
2021-02-25 1:46 ` Eric Sandeen
2021-02-25 1:56 ` Qu Wenruo
2021-02-25 2:45 ` Eric Sandeen
2021-02-25 3:13 ` Qu Wenruo
2021-02-25 3:15 ` Eric Sandeen
2021-02-25 3:18 ` Qu Wenruo
2021-02-26 3:10 ` 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=5e133067-ec0c-f2c6-7fb6-84620e26881e@sandeen.net \
--to=sandeen@sandeen.net \
--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 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).