From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Neil Brown <neilb@suse.de>,
Daniel Reurich <daniel@centurion.net.nz>,
linux-raid <linux-raid@vger.kernel.org>,
567468@bugs.debian.org
Subject: Re: (boot time consequences of) Linux mdadm superblock question.
Date: Fri, 19 Feb 2010 10:16:19 +0100 [thread overview]
Message-ID: <20100219091619.GA2964@lazy.lzy> (raw)
In-Reply-To: <20100219004237.GC25162@lapse.rw.madduck.net>
Hi,
> True. You'd have to update the superblock UUID right after creation
> of the filesystem. That doesn't sound like a robust strategy to
> making mdadm.conf optional.
it seems that, with "dracut", "mdadm.conf" is optional.
There is the kernel boot paramenter "rd_NO_MDADMCONF",
which forces "dracut" to do not use the "mdadm.conf" in
the initramfs image.
This seems to work also if / is on mdX.
I just tried it, and it was running fine. I did not check
the details, i.e. I've no proof "dracut" was not cheating.
My impression is that it uses the "mdadm -I" functionality.
There are other interesting kernel boot options, like:
rd_MD_UUID=<md uuid>
bye,
--
piergiorgio
next prev parent reply other threads:[~2010-02-19 9:16 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 1:51 Linux mdadm superblock question Volker Armin Hemmann
2010-02-14 4:02 ` Michael Evans
2010-02-14 7:21 ` david
2010-02-14 8:38 ` Michael Evans
2010-02-14 18:40 ` Volker Armin Hemmann
2010-02-14 18:53 ` John Robinson
2010-02-14 21:16 ` Gabor Gombas
[not found] ` <201002142013.24922.volkerarmin@googlemail.com>
2010-02-16 14:28 ` John Robinson
2010-02-16 14:37 ` Volker Armin Hemmann
2010-02-16 14:46 ` Robin Hill
2010-02-16 17:23 ` John Robinson
2010-02-16 19:38 ` Luca Berra
2010-02-16 17:18 ` Bill Davidsen
2010-02-16 21:06 ` Volker Armin Hemmann
2010-02-16 22:00 ` Nick Bowler
2010-02-16 22:18 ` Volker Armin Hemmann
2010-02-17 14:25 ` Nick Bowler
2010-02-18 9:27 ` Ian Dall
2010-02-17 1:03 ` Mr. James W. Laferriere
2010-02-17 2:01 ` Neil Brown
2010-02-17 2:38 ` Volker Armin Hemmann
2010-02-17 23:15 ` Neil Brown
2010-02-17 6:34 ` Kyle Moffett
2010-02-17 9:38 ` Rudy Zijlstra
2010-02-17 13:26 ` Frans Pop
2010-02-17 20:54 ` Gabor Gombas
2010-02-17 21:29 ` Frans Pop
2010-02-18 3:40 ` Goswin von Brederlow
2010-02-17 16:22 ` Kyle Moffett
2010-02-17 17:41 ` david
2010-02-17 18:10 ` Nick Bowler
2010-02-17 18:27 ` Volker Armin Hemmann
2010-02-17 18:37 ` Nick Bowler
2010-02-17 18:41 ` david
2010-02-17 18:51 ` Nick Bowler
2010-02-17 21:17 ` david
2010-02-17 21:37 ` Nick Bowler
2010-02-17 22:21 ` david
2010-02-17 22:29 ` boot times, not mdadm (was: Linux mdadm superblock question.) martin f krafft
2010-02-17 23:24 ` (boot time consequences of) Linux mdadm superblock question Neil Brown
2010-02-17 23:50 ` martin f krafft
2010-02-18 2:58 ` Henrique de Moraes Holschuh
2010-02-18 3:26 ` martin f krafft
2010-02-18 4:03 ` Daniel Reurich
2010-02-18 4:40 ` martin f krafft
2010-02-18 5:10 ` Neil Brown
2010-02-18 5:21 ` martin f krafft
2010-02-18 5:34 ` Neil Brown
2010-02-19 0:42 ` martin f krafft
2010-02-19 2:51 ` Daniel Reurich
[not found] ` <20100221171445.GB17267@lapse.rw.madduck.net>
2010-02-22 7:06 ` Goswin von Brederlow
2010-02-22 7:37 ` Bug#567468: " Michael Evans
2010-02-22 9:14 ` martin f krafft
2010-02-22 9:11 ` martin f krafft
2010-02-22 10:42 ` Daniel Reurich
2010-02-19 9:16 ` Piergiorgio Sartor [this message]
[not found] ` <20100221174007.GB19058@lapse.rw.madduck.net>
[not found] ` <20100221201304.GB2570@lazy.lzy>
2010-02-22 9:16 ` Bug#567468: md homehost (was: Bug#567468: (boot time consequences of) Linux mdadm superblock) question martin f krafft
2010-02-22 11:11 ` Daniel Reurich
2010-02-23 7:29 ` md homehost Goswin von Brederlow
2010-02-23 8:10 ` martin f krafft
2010-02-23 2:30 ` md homehost (was: Bug#567468: (boot time consequences of) Linux mdadm superblock) question Neil Brown
2010-02-23 6:27 ` martin f krafft
2010-02-23 7:31 ` md homehost Goswin von Brederlow
2010-02-23 8:16 ` Bug#567468: " martin f krafft
2010-02-24 13:13 ` Goswin von Brederlow
2010-02-24 17:52 ` Mario 'BitKoenig' Holbe
2010-02-24 22:23 ` Neil Brown
2010-02-23 8:18 ` Piergiorgio Sartor
2010-02-24 0:10 ` md homehost (was: Bug#567468: (boot time consequences of) Linux mdadm superblock) question Neil Brown
2010-02-24 4:12 ` Michael Evans
2010-02-24 13:41 ` md homehost Goswin von Brederlow
2010-02-24 22:30 ` Neil Brown
2010-02-25 7:16 ` Goswin von Brederlow
2010-02-25 7:46 ` Neil Brown
2010-02-25 8:33 ` Michael Evans
2010-02-25 11:55 ` Mario 'BitKoenig' Holbe
2010-02-18 5:17 ` (boot time consequences of) Linux mdadm superblock question Daniel Reurich
2010-02-18 5:22 ` martin f krafft
2010-02-17 18:46 ` Volker Armin Hemmann
2010-02-17 22:26 ` H. Peter Anvin
2010-02-18 3:33 ` Goswin von Brederlow
2010-02-18 7:51 ` Luca Berra
2010-02-18 14:12 ` Nick Bowler
2010-02-19 9:04 ` Michael Evans
2010-02-14 19:34 ` Henrique de Moraes Holschuh
2010-02-14 20:07 ` Michael Evans
2010-02-14 21:14 ` Henrique de Moraes Holschuh
2010-02-14 20:47 ` Asdo
2010-02-14 21:26 ` Henrique de Moraes Holschuh
2010-02-14 21:28 ` Gabor Gombas
2010-02-15 9:08 ` martin f krafft
2010-02-15 7:51 ` Luca Berra
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=20100219091619.GA2964@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=567468@bugs.debian.org \
--cc=daniel@centurion.net.nz \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).