public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fun with mdadm (Software RAID)
Date: Sat, 21 Dec 2024 16:36:06 +0000	[thread overview]
Message-ID: <Z2budoEVxMRTiL9W@MAC.fritz.box> (raw)
In-Reply-To: <Z2a4Bvt0zX7vtSsL@MAC.fritz.box>

Hello again, Karl.

On Sat, Dec 21, 2024 at 12:43:50 +0000, Alan Mackenzie wrote:
> On Fri, Dec 20, 2024 at 23:02:58 +0100, karl@aspodata.se wrote:
> > Alan Mackenzie:
> > > On Fri, Dec 20, 2024 at 18:44:53 +0100, karl@aspodata.se wrote:
> > ...
> > > > Please tell if you make booting with metadata 1.2 work.
> > > > I havn't tested that.

> > > I've just tried it, with metadata 1.2, and it doesn't work.  I got error
> > > messages at boot up to the effect that the component partitions were
> > > lacking valid version 0.0 super blocks.

> > > People without initramfs appear not to be in the sights of the
> > > maintainers of this software.  They could so easily have made the
> > > assembly of metadata 1.2 components on the kernel command line work.
> > > :-(
> > ...

I've now got working code which assembles a metadata 1.2 RAID array at
boot time.  The syntax needed on the command line is, again,

    md=124,1.2,/dev/nvme0n1p6,/dev/nvme1n1p6

..  In place of 1.2 can be any of 0.90, 1.0, 1.1, though I haven't tested
it with anything but 1.2 as yet.

> The pertinent functions are mainly in drivers/md/md-autodetect.c and
> md.c (same directory).

Actually, just in md-autodetect.c.

[ .... ]

> Nevertheless, I might make the above enhancement, just because.

Done.

> > Regards,
> > /Karl Hammar

-- 
Alan Mackenzie (Nuremberg, Germany).


  reply	other threads:[~2024-12-21 16:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 10:47 [gentoo-user] Fun with mdadm (Software RAID) Alan Mackenzie
2024-12-20 14:50 ` karl
2024-12-20 15:28   ` Alan Mackenzie
2024-12-20 17:44     ` karl
2024-12-20 20:19       ` Alan Mackenzie
2024-12-20 20:38         ` Hoël Bézier
2024-12-20 20:53           ` Alan Mackenzie
2024-12-20 22:02         ` karl
2024-12-30  4:08           ` Frank Steinmetzger
2024-12-20 22:02         ` karl
2024-12-21 12:43           ` Alan Mackenzie
2024-12-21 16:36             ` Alan Mackenzie [this message]
2024-12-21 16:45               ` karl
2024-12-21 16:58                 ` Alan Mackenzie
2024-12-22 13:08                   ` Alan Mackenzie
2024-12-22 12:16             ` Wols Lists
2024-12-22 12:08         ` Wols Lists
2024-12-22 12:02       ` Wols Lists
2024-12-22 13:43         ` Alan Mackenzie
2024-12-22 15:29           ` Peter Humphrey
2024-12-22 16:53             ` Wols Lists
2024-12-22 20:05               ` Alan Mackenzie
2024-12-25 21:16                 ` Steven Lembark

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=Z2budoEVxMRTiL9W@MAC.fritz.box \
    --to=acm@muc.de \
    --cc=gentoo-user@lists.gentoo.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