From: Michael Prokop <mika@debian.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: 737951@bugs.debian.org, linux-raid <linux-raid@vger.kernel.org>
Subject: Bug#737951: mdadm: udev rules files ignores raid=noautodetect kernel parameter
Date: Mon, 10 Feb 2014 16:53:05 +0100 [thread overview]
Message-ID: <2014-02-10T16-46-44@devnull.michael-prokop.at> (raw)
In-Reply-To: <52F48D0E.80905@msgid.tls.msk.ru>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Hi,
thanks for the fast reply, Michael
* Michael Tokarev [Fri Feb 07, 2014 at 11:36:46AM +0400]:
> 07.02.2014 11:21, Michael Prokop wrote:
> > It would be nice if there would be some way (maybe just checking for
> > raid=noautodetect in /proc/cmdline?) to disable auto assembly
> > without having to manually delete/override the udev file.
> I don't think that using raid=noautodetect is a good way of doing
> this. It is for the really obsolete in-kernel array assembly, and
> it is described as such in the documentation you quoted above.
Right
[...]
> None of these parameters, at my point of view, should be considered
> after pre-boot is done and we're in the main system. If you're
> talking about main udev rules of mdadm, I disagree, there should
> be entirely separate option, if at all.
> What is your usage case? What are you trying to achieve?
[...]
My goal is to support booting a live system (like http://grml.org/)
in a way which *prevents* auto assembling under all circumstances.
This is relevant e.g. for data rescue and forensics tasks.
regards,
-mika-
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2014-02-10 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2014-02-07T08-14-24@devnull.michael-prokop.at>
2014-02-07 7:36 ` Bug#737951: mdadm: udev rules files ignores raid=noautodetect kernel parameter Michael Tokarev
2014-02-10 15:53 ` Michael Prokop [this message]
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=2014-02-10T16-46-44@devnull.michael-prokop.at \
--to=mika@debian.org \
--cc=737951@bugs.debian.org \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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 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.