From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Cc: hch@lst.de, linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs: disguise single-data-RAID56 as RAID1/RAID1C3
Date: Mon, 13 Jul 2026 18:49:37 +0930 [thread overview]
Message-ID: <32c03d5d-d5b4-4954-9bc7-d7f64e46fda1@suse.com> (raw)
In-Reply-To: <cover.1779412152.git.wqu@suse.com>
Hi David,
I know you hate this way to fix the problem, but considering it's
already 7.2-rc3, if you do not like this method I think it's time for
you to submit your alternative.
My existing patches still apply on the latest for-next and is known to
avoid the extra warning from RAID6 lib.
Thanks,
Qu
在 2026/5/22 18:53, Qu Wenruo 写道:
> [CHANGELOG]
> RFC->v1:
> - Remove unused btrfs_chunk_map::io_(align|width) members
> To make space for the new member.
>
> - Fix a duplicated bg->flags assignment in fill_dummy_bgs()
> Just exposed by the last patch which also touches that code.
>
> - Use a dedicated member to record the on-disk chunk type
> So it's less fragile than the RFC patch.
>
> The single-data-RAID56 (2 disks raid5 or 3 disks raid6) is not a feature
> that should be supported in the first place, thus raid56 is going to
> remove such support.
>
> Meanwhile rejecting single-data-RAID56 will cause existing btrfs users
> unable to mount their fs, even if there is only a single
> empty chunk with that flag, mostly caused by some degraded mount.
>
> So to avoid impacting existing users, implement an internal
> single-data-RAID56 to RAID1/RAID1C3 mapping, to co-operate with the
> upstream raid56 lib changes.
>
> Qu Wenruo (3):
> btrfs: remove btrfs_chunk_map::io_(align|width) members
> btrfs: remove duplicated block group type assignment
> btrfs: disguise single-data-RAID56 as RAID1/RAID1C3
>
> fs/btrfs/block-group.c | 3 +--
> fs/btrfs/volumes.c | 25 ++++++++++++++++++-------
> fs/btrfs/volumes.h | 10 ++++++++--
> 3 files changed, 27 insertions(+), 11 deletions(-)
>
prev parent reply other threads:[~2026-07-13 9:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 9:23 [PATCH 0/3] btrfs: disguise single-data-RAID56 as RAID1/RAID1C3 Qu Wenruo
2026-05-22 9:23 ` [PATCH 1/3] btrfs: remove btrfs_chunk_map::io_(align|width) members Qu Wenruo
2026-05-22 9:23 ` [PATCH 2/3] btrfs: remove duplicated block group type assignment Qu Wenruo
2026-05-22 9:23 ` [PATCH 3/3] btrfs: disguise single-data-RAID56 as RAID1/RAID1C3 Qu Wenruo
2026-05-23 14:23 ` David Sterba
2026-05-23 22:46 ` Qu Wenruo
2026-05-24 4:13 ` Qu Wenruo
2026-05-25 10:12 ` David Sterba
2026-05-25 10:25 ` Qu Wenruo
2026-05-25 6:00 ` Christoph Hellwig
2026-05-25 10:17 ` David Sterba
2026-05-25 10:39 ` Qu Wenruo
2026-05-26 6:46 ` Christoph Hellwig
2026-05-26 6:45 ` Christoph Hellwig
2026-07-13 9:19 ` 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=32c03d5d-d5b4-4954-9bc7-d7f64e46fda1@suse.com \
--to=wqu@suse.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-raid@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