From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: jes@trained-monkey.org
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH v2] mdadm: fix update=resync regression
Date: Tue, 13 Feb 2024 16:18:02 +0100 [thread overview]
Message-ID: <20240213161802.000015a1@linux.intel.com> (raw)
In-Reply-To: <20240209130216.19055-1-mariusz.tkaczyk@linux.intel.com>
On Fri, 9 Feb 2024 14:02:16 +0100
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com> wrote:
> mdadm --assemble --update=resync started failing with the error
> "mdadm: --update=resync not understood for 1.x metadata".
>
> It is a regression. Add omitted branch to fix error.
>
> Resubmitted, original author is not responding.
> https://lore.kernel.org/linux-raid/ZZqJlCToUS3Qrl4J@bianca.dpss.psy.unipd.it/
>
> Fixes: 7e8daba8b793 ("super1: refactor the code for enum")
> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
> ---
No comments, Applied!
Thanks,
Mariusz
prev parent reply other threads:[~2024-02-13 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 13:02 [PATCH v2] mdadm: fix update=resync regression Mariusz Tkaczyk
2024-02-13 15:18 ` Mariusz Tkaczyk [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=20240213161802.000015a1@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=jes@trained-monkey.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;
as well as URLs for NNTP newsgroup(s).