From: Mariusz Tkaczyk <mtkaczyk@kernel.org>
To: Nigel Croxon <ncroxon@redhat.com>
Cc: linux-raid@vger.kernel.org, mariusz.tkaczyk@linux.intel.com,
Xiao Ni <xni@redhat.com>
Subject: Re: [PATCH] mdadm: Incremental mode creates file for udev rules
Date: Wed, 26 Mar 2025 13:48:21 +0100 [thread overview]
Message-ID: <20250326134821.305ab2d8@mtkaczyk-private-dev> (raw)
In-Reply-To: <ded3b88e-c0e8-4a66-89f3-43bc6bb9664a@redhat.com>
On Tue, 25 Mar 2025 15:18:00 -0400
Nigel Croxon <ncroxon@redhat.com> wrote:
> Mounting an md device may fail during boot from mdadm's claim
> on the device not being released before systemd attempts to mount.
>
> While mdadm is still constructing the array (mdadm --incremental
> that is called from within
> /usr/lib/udev/rules.d/64-md-raid-assembly.rules), there is an attempt
> to mount the md device, but there is not a creation of
> "/run/mdadm/creating-xxx" file when in incremental mode that the rule
> is looking for. Therefore the device is not marked as
> SYSTEMD_READY=0 in "/usr/lib/udev/rules.d/01-md-raid-creating.rules"
> and missing synchronization using the "/run/mdadm/creating-xxx" file.
>
> Enable creating the "/run/mdadm/creating-xxx" file during
> incremental mode.
Hi Nigel,
The code is rather simple but the change is big. Before I will consider
it is safe to merge please describe the particular scenario you are
fixing.
It is known, persistent issue? Is is sporadic issue?
In the commit message please add why you think it is safe change.
This will affect every environment. We need to be certain that it will
not bring regression in booting flow. It might be hard to debug and
have big impact on users.
Thanks,
Mariusz
>
> Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
> ---
> Incremental.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
next prev parent reply other threads:[~2025-03-26 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 19:18 [PATCH] mdadm: Incremental mode creates file for udev rules Nigel Croxon
2025-03-26 2:31 ` Xiao Ni
2025-03-26 8:00 ` Paul Menzel
2025-03-26 9:15 ` Paul Menzel
2025-03-26 12:48 ` Mariusz Tkaczyk [this message]
2025-03-26 17:36 ` Nigel Croxon
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=20250326134821.305ab2d8@mtkaczyk-private-dev \
--to=mtkaczyk@kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=ncroxon@redhat.com \
--cc=xni@redhat.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