From: Felix Lechner via Guix-patches via <guix-patches@gnu.org>
To: Andreas Enge <andreas@enge.fr>
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 08:46:24 -0800 [thread overview]
Message-ID: <87zfx2zj1b.fsf@lease-up.com> (raw)
In-Reply-To: <Zak4KDD1lrMPqt5r@jurong>
Hi Andreas,
On Thu, Jan 18 2024, Andreas Enge wrote:
> when I wrote the code for bayfront, we needed to wait a bit until the
> hard disks appeared.
How long ago? I never needed it on six pieces of equipment of varying
dimensions, including an SAS server (with reflashed Dell equipment, if
that's what Bayfront is using) and a VM with NVMe SSDs.
Either way, accepting this patch as is now will not break anything. We
introduce a new mapping (md-device-mapping) that can be used to
reconfigure Bayfront at the maintainer's leisure.
It would be easy to react to a bug report later while Bayfront continues
to use raid-device-mapping..
Kind regards
Felix
next prev parent reply other threads:[~2024-01-18 16:47 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
2024-01-18 16:46 ` Felix Lechner via Guix-patches via [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfx2zj1b.fsf@lease-up.com \
--to=guix-patches@gnu.org \
--cc=64259@debbugs.gnu.org \
--cc=andreas@enge.fr \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.