From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/3] btrfs-progs: filesystem-usage: handle missing seed device properly
Date: Mon, 20 Mar 2023 16:48:02 +0100 [thread overview]
Message-ID: <20230320154802.GG10580@suse.cz> (raw)
In-Reply-To: <ee689112-30de-89b3-51fc-cc6bc33716fb@gmx.com>
On Sat, Mar 18, 2023 at 08:00:18AM +0800, Qu Wenruo wrote:
> Hi David,
>
> Mind to drop the series?
>
> Although the series is to solve the btrfs/249 failure, Anand's patch is
> already merged.
>
> Furthermore the situation of btrfs/249 is very niche, it involves RAID1
> as seed, which should be rare or even non-exist in real world.
>
> Thus I don't think the fallback for such a niche usage is really worthy
> anymore.
The multi-device seeding should work, though I agree it's a niche use
case. A fallback code should be there either in full or with a warning
that some combination is not supported or could be problematic.
next prev parent reply other threads:[~2023-03-20 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 11:50 [PATCH 0/3] btrfs-progs: fix btrfs/249 failure Qu Wenruo
2023-02-11 11:50 ` [PATCH 1/3] btrfs-progs: filesystem-usage: handle missing seed device properly Qu Wenruo
2023-03-16 15:25 ` David Sterba
2023-03-18 0:00 ` Qu Wenruo
2023-03-20 15:48 ` David Sterba [this message]
2023-02-11 11:50 ` [PATCH 2/3] btrfs-progs: sync ioctl from kernel Qu Wenruo
2023-03-16 15:27 ` David Sterba
2023-03-18 0:00 ` Qu Wenruo
2023-02-11 11:50 ` [PATCH 3/3] btrfs-progs: filesystem-usage: use btrfs_ioctl_dev_info_args::fsid to determine if a device is seed 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=20230320154802.GG10580@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--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