From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Colin S <linux-btrfs-ml@zetafleet.com>, linux-btrfs@vger.kernel.org
Subject: Re: Converting RAID1 to single fails if RAID1 is missing device
Date: Mon, 3 Feb 2025 16:43:03 +1030 [thread overview]
Message-ID: <48bf3e3c-52a5-4fec-b399-93ababfa025d@gmx.com> (raw)
In-Reply-To: <ef9dfa64-63f8-47ad-9857-d40aecb20546@zetafleet.com>
在 2025/2/3 15:52, Colin S 写道:
> On 02/02/2025 20:32, Qu Wenruo wrote:
>>
>> But I think the ultimate solution is to make btrfs to properly detect
>> and support device shut down request.
>
> Yes. How many years and how many more users need to have this problem
> before it’s given some priority?
Complaining is so easy that some one doesn't even know what's going
wrong can do.
>
>> Although that would also introduce new complexity, e.g. what if the
>> missing devices show up again after missing several writes?
>
> Since I see you wrote a patch in 2022 to add write-intent bitmap for
> raid5/6, don’t you already understand the answer is a write-intent
> bitmap? Further, did you not see any of the several messages I have sent
> to the mailing list talking about exactly this in the last year? I am
> genuinely confused.
>
It's completely a different bug.
It doesn't even have RAID56 involved.
And write-intent bitmap is not the solution at all. It doesn't support
things like zoned device support (which is now part of the core btrfs
functionality).
Knowing what you don't know is important.
next prev parent reply other threads:[~2025-02-03 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 22:43 Converting RAID1 to single fails if RAID1 is missing device Jeff Siddall
2025-02-03 0:44 ` Qu Wenruo
2025-02-03 1:11 ` Jeff Siddall
2025-02-03 2:19 ` Jussi Kansanen
2025-02-03 2:32 ` Qu Wenruo
2025-02-03 5:22 ` Colin S
2025-02-03 6:13 ` Qu Wenruo [this message]
2025-02-04 7:04 ` Colin S
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=48bf3e3c-52a5-4fec-b399-93ababfa025d@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs-ml@zetafleet.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.