From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Anand Jain <anand.jain@oracle.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH v2] fstests: generic/730: exclude btrfs for now
Date: Wed, 4 Jun 2025 18:43:07 +0930 [thread overview]
Message-ID: <3fa2ea39-ffaa-4732-bf9c-8ae9636d0a9e@gmx.com> (raw)
In-Reply-To: <bf4a8a9f-16cc-467d-a039-2a5705ac52f6@oracle.com>
在 2025/6/4 17:40, Anand Jain 写道:
> On 6/4/2025 3:10 PM, Qu Wenruo wrote:
>> The test case always fail for btrfs:
>>
>> generic/730 - output mismatch (see /home/adam/xfstests-dev/
>> results//generic/730.out.bad)
>> --- tests/generic/730.out 2024-04-25 18:13:45.203549435 +0930
>> +++ /home/adam/xfstests-dev/results//generic/730.out.bad
>> 2025-06-04 15:10:39.062430952 +0930
>> @@ -1,2 +1 @@
>> QA output created by 730
>> -cat: -: Input/output error
>> ...
>
>
>
> [PATCH v1 5/7] generic/730: add _require_scratch_shutdown
That works fine for btrfs, but that's only for now.
The _require_scratch_shutdown is only going to check the shutdown ioctl,
not the per-block-device shutdown.
I guess this means for fs supporting per-bdev shutdown, it must have a
dedicated shutdown ioctl.
Thanks,
Qu>
> Fixed it.
>
>
>>
>> The root reason is that, btrfs doesn't implement its blk_holder_ops when
>> opening a block device.
>> Thus when the underlying block device is marked dead, btrfs is never
>> going to know thus no way to shutdown (nor btrfs has a way to shutdown
>> either).
>>
>> I'm trying to improve the situation, but until then just exlucde btrfs
>> from the test case for now.
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>> ---
>> Changelog:
>> v2:
>> - Update the root reason
>> It's not the sb->s_op->shutdown, that is only for single device
>> fs (through fs_bdev_mark_dead()).
>> For a multi-devices fs, it should provide a blk_holder_ops when
>> opening the block device.
>
> Along with that, I think it is a good idea to bring XFS_IOC_GOINGDOWN,
> per fs (all devices in a multi-device fs) and vfs level so that we could
> support unmount --force.
>
>> +if [ "$FSTYP" = "btrfs" ]; then
>> + _notrun "btrfs doesn't support per-fs shutdown yet"
>> +fi
>> +
>
> _require_scratch_shutdown() will take care.
>
>
> Thanks, Anand
>
prev parent reply other threads:[~2025-06-04 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 7:10 [PATCH v2] fstests: generic/730: exclude btrfs for now Qu Wenruo
2025-06-04 8:10 ` Anand Jain
2025-06-04 9:13 ` Qu Wenruo [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=3fa2ea39-ffaa-4732-bf9c-8ae9636d0a9e@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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