From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: Naohiro Aota <Naohiro.Aota@wdc.com>,
"hch@infradead.org" <hch@infradead.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Re: [PATCH] btrfs/294: reject zoned devices for now
Date: Tue, 25 Jul 2023 18:11:03 +0200 [thread overview]
Message-ID: <20230725161103.GH20457@twin.jikos.cz> (raw)
In-Reply-To: <f0695163-d613-52e3-3443-2921dc2153c3@suse.com>
On Tue, Jul 25, 2023 at 08:58:34AM +0800, Qu Wenruo wrote:
>
>
> On 2023/7/25 08:22, Naohiro Aota wrote:
> > On Mon, Jul 24, 2023 at 07:10:51AM -0700, Christoph Hellwig wrote:
> >> On Mon, Jul 24, 2023 at 11:04:23AM +0800, Qu Wenruo wrote:
> >>> The test case itself is utilizing RAID5/6, which is not yet supported on
> >>> zoned device.
> >>>
> >>> In the future we would use raid-stripe-tree (RST) feature, but for now
> >>> just reject zoned devices completely.
> >>>
> >>> And since we're here, also update the _fixed_by_kernel_commit lines, as
> >>> the proper fix is already merged upstream.
> >>
> >> Hmm, instead of spreading these checks, shouldn't we check that the
> >> RAID level is supported, and have one single nob for that based off
> >> it, similar to _btrfs_get_profile_configs()?
> >>
> >
> > That's beneficial. We need to declare which profile the test going to use,
> > something like this?
> >
> > _btrfs_require_profile raid5 raid6
> >
> > or
> >
> > _btrfs_require_profile data:dup
> >
> > as the zoned mode cannot work with the DUP profile for data.
>
> The latter one sounds good, considering zoned support differs for data
> and metadata profiles.
>
> Another thing is, do we have any sysfs files to indicate what profiles
> we support?
> For now we only have a "zoned" features, but no dedicated zoned specific
> sysfs files.
>
> Would that be a good thing to consider?
We don't have it but I think it's a good idea not just for testing, we
export other information as the "features/supported_..." files. The
profiles don't change often but with the incremental support for zoned
this would make it easier for tests to keep up.
next prev parent reply other threads:[~2023-07-25 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 3:04 [PATCH] btrfs/294: reject zoned devices for now Qu Wenruo
2023-07-24 4:55 ` Zorro Lang
2023-07-24 6:19 ` Naohiro Aota
2023-07-24 14:10 ` Christoph Hellwig
2023-07-25 0:22 ` Naohiro Aota
2023-07-25 0:58 ` Qu Wenruo
2023-07-25 16:11 ` David Sterba [this message]
2023-07-27 15:50 ` Zorro Lang
2023-07-27 22:15 ` Qu Wenruo
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=20230725161103.GH20457@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Naohiro.Aota@wdc.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.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