From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: jes@trained-monkey.org
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH v2] Revert "mdadm: remove container_enough logic"
Date: Fri, 9 Feb 2024 09:11:42 +0100 [thread overview]
Message-ID: <20240209091142.00006534@linux.intel.com> (raw)
In-Reply-To: <20240205145029.12022-1-mariusz.tkaczyk@linux.intel.com>
On Mon, 5 Feb 2024 15:50:29 +0100
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com> wrote:
> Mentioned patch changes way of IMSM member arrays assembling, they are
> updated by every new drive incremental processes. Previously, member
> arrays were created and filled once, by last drive incremental process.
>
> We determined regressions with various impact. Unfortunately, initial
> testing didn't show them.
>
> Regressions are connected to drive appearance order and may not be
> reproducible on every configuration, there are at least two know
> issues for now:
>
> - sysfs attributes are filled using old metadata if there is
> outdated drive and it is enumerated first.
>
> - rebuild may be aborted and started from beginning after reboot,
> if drive under rebuild is enumerated as the last one.
>
> This reverts commit 4dde420fc3e24077ab926f79674eaae1b71de10b. It fixes
> checkpatch issues and reworks logic to remove empty "if" branch in
> Incremental.
>
> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
No comments, Applied!
Thanks,
Mariusz
prev parent reply other threads:[~2024-02-09 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 14:50 [PATCH v2] Revert "mdadm: remove container_enough logic" Mariusz Tkaczyk
2024-02-09 8:11 ` 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=20240209091142.00006534@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 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.