From: Jeremy Katz <katzj@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: David Zeuthen <david@fubar.dk>,
Hans de Goede <hdegoede@redhat.com>,
initramfs <initramfs@vger.kernel.org>,
linux-hotplug@vger.kernel.org, "Danecki,
Jacek" <jacek.danecki@intel.com>,
Harald Hoyer <harald@redhat.com>,
Doug Ledford <dledford@redhat.com>, NeilBrown <neilb@suse.de>
Subject: Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
Date: Thu, 16 Jul 2009 00:16:52 +0000 [thread overview]
Message-ID: <20090716001651.GB45537@redhat.com> (raw)
In-Reply-To: <e9c3a7c20907151147q3e48e681ufd0916f6e4e390c4@mail.gmail.com>
On Wednesday, July 15 2009, Dan Williams said:
> mdadm-3.0 has facilities to prevent assembly of certain metadata types
> [1] or arrays with certain uuids [2]. I wonder if we also need a
> facility to prevent auto-assembly of arrays *not* listed in
> mdadm.conf? So the mdadm.conf file installed in the initramfs would
> only identify the root array and all other randomly identified md
> devices would be ignored (rather than assembled with a foreign name).
>
> Thoughts?
There is no mdadm.conf in the initramfs -- in fact, the initramfs may
not even be generated on the system that you're booting and instead be
"generic" for the kernel in question
Jeremy
next prev parent reply other threads:[~2009-07-16 0:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 9:57 RFC: mdadm and bringing up raid sets from initrd (dracut) Hans de Goede
2009-07-14 13:39 ` Doug Ledford
[not found] ` <1955210A-EF27-479F-8C58-BA4FA9018A56-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-14 14:01 ` Hans de Goede
2009-07-14 14:14 ` Doug Ledford
[not found] ` <D758972F-0E5A-4860-9011-6B2DA1FA771A-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-14 15:00 ` David Zeuthen
2009-07-16 10:56 ` Harald Hoyer
[not found] ` <4A5C6501.3080607-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-14 14:30 ` David Zeuthen
[not found] ` <1247581847.1991.16.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-07-15 18:47 ` Dan Williams
2009-07-16 0:16 ` Jeremy Katz [this message]
[not found] ` <20090716001651.GB45537-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-16 7:11 ` Victor Lowther
2009-07-16 10:56 ` Neil Brown
2009-07-16 11:09 ` Neil Brown
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=20090716001651.GB45537@redhat.com \
--to=katzj@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@fubar.dk \
--cc=dledford@redhat.com \
--cc=harald@redhat.com \
--cc=hdegoede@redhat.com \
--cc=initramfs@vger.kernel.org \
--cc=jacek.danecki@intel.com \
--cc=linux-hotplug@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).