From: Yu Kuai <yukuai1@huaweicloud.com>
To: Song Liu <song@kernel.org>, Yu Kuai <yukuai1@huaweicloud.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH md-6.13] md: remove bitmap file support
Date: Fri, 8 Nov 2024 09:03:25 +0800 [thread overview]
Message-ID: <ef4dcb9e-a2fa-d9dc-70c1-e58af6e71227@huaweicloud.com> (raw)
In-Reply-To: <CAPhsuW7Ry0iUs6X7P4jL5CX3+8EGfb5uL=g-q_8jVR-g19ummQ@mail.gmail.com>
Hi,
在 2024/11/08 7:41, Song Liu 写道:
> On Thu, Nov 7, 2024 at 5:02 AM Yu Kuai <yukuai1@huaweicloud.com> wrote:
>>
>> From: Yu Kuai <yukuai3@huawei.com>
>>
>> The bitmap file has been marked as deprecated for more than a year now,
>> let's remove it, and we don't need to care about this case in the new
>> bitmap.
>>
>> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
>
> What happens when an old array with bitmap file boots into a kernel
> without bitmap file support?
If mdadm is used with bitmap file support, then kenel will just ignore
the bitmap, the same as none bitmap. Perhaps it's better to leave a
error message?
And if mdadm is updated, reassemble will fail.
Thanks,
Kuai
>
> Thanks,
> Song
> .
>
next prev parent reply other threads:[~2024-11-08 1:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 12:59 Yu Kuai
2024-11-07 23:41 ` Song Liu
2024-11-08 1:03 ` Yu Kuai [this message]
2024-11-08 1:28 ` Song Liu
2024-11-08 1:33 ` Yu Kuai
2024-11-08 5:15 ` Dragan Milivojević
2024-11-08 6:07 ` Yu Kuai
2024-11-08 22:19 ` Dragan Milivojević
2024-11-09 1:43 ` Yu Kuai
2024-11-09 2:15 ` Dragan Milivojević
2024-11-11 2:04 ` Yu Kuai
2024-11-11 11:59 ` Dragan Milivojević
2024-11-11 13:02 ` Yu Kuai
2024-11-11 14:07 ` Dragan Milivojević
2024-11-13 1:18 ` Yu Kuai
2024-11-13 1:25 ` Dragan Milivojević
2024-11-12 7:54 ` Mariusz Tkaczyk
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=ef4dcb9e-a2fa-d9dc-70c1-e58af6e71227@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®