From: Andreas Enge <andreas@enge.fr>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: 64259@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#64259] [PATCH 2/2] Provide md-array-device-mapping to start MD arrays via UUID or name.
Date: Thu, 18 Jan 2024 15:39:36 +0100 [thread overview]
Message-ID: <Zak4KDD1lrMPqt5r@jurong> (raw)
In-Reply-To: <87fs22pn6a.fsf@lease-up.com>
Hello,
Am Sun, Oct 22, 2023 at 10:44:13AM -0700 schrieb Felix Lechner:
> > Does the busy wait loop currently in ‘open-raid-device’ need to be
> > preserved?
> I personally do not believe so but I'll defer to Andreas Enge, whom I
> copied on this message. I believe Andreas wrote the original device
> mapping.
well, I do not know whether it is still needed. It appears that when
I wrote the code for bayfront, we needed to wait a bit until the hard
disks appeared. Are there reasons to believe that this has changed
in the meantime?
Andreas
next prev parent reply other threads:[~2024-01-18 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 2:05 [bug#64259] [PATCH 0/2] Allow booting of degraded software RAID/MD arrays Felix Lechner via Guix-patches via
2023-06-24 2:07 ` [bug#64259] [PATCH 1/2] Offer an mdadm variant of uuids Felix Lechner via Guix-patches via
2023-06-24 2:07 ` [bug#64259] [PATCH 2/2] Provide md-array-device-mapping to start MD arrays via UUID or name Felix Lechner via Guix-patches via
2023-10-20 21:55 ` Ludovic Courtès
2023-10-22 17:44 ` Felix Lechner via Guix-patches via
2024-01-18 14:39 ` Andreas Enge [this message]
2024-01-18 16:46 ` Felix Lechner via Guix-patches via
2024-01-18 16:51 ` Andreas Enge
2023-11-23 14:56 ` [bug#64259] [PATCH v2 1/2] Offer an mdadm variant of uuids Felix Lechner via Guix-patches via
2023-11-23 14:57 ` [bug#64259] [PATCH v2 2/2] Provide md-array-device-mapping to start MD arrays via UUID or name Felix Lechner via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zak4KDD1lrMPqt5r@jurong \
--to=andreas@enge.fr \
--cc=64259@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).