linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stefan Hübner" <stefan.huebner@stud.tu-ilmenau.de>
To: Neil Brown <neilb@suse.de>
Cc: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>,
	linux-raid@vger.kernel.org
Subject: Re: turn off auto assembly
Date: Mon, 06 Dec 2010 22:52:56 +0100	[thread overview]
Message-ID: <4CFD5B38.2090801@stud.tu-ilmenau.de> (raw)
In-Reply-To: <20101203123009.0aa23102@notabene.brown>

Thanks for all the hints.

There were no udev-rules on the computers, so I fixed the problem using
Neil's hints: 'echo "AUTO -all" >> /etc/mdadm.conf'.

Cheers,
Stefan

P.S.: as the "auto assemble everything with 0xfd partition type" may
become destructive at times (I have to deal a lot with damaged arrays),
I'd suggest not to make it the default setting.  But the other side is:
most people who set up a RAID would want to have it this way, so I guess
it's my duty to make sure no autoassembly on my technicians' computers
happens, unless I tell mdadm to do so...

P.P.S.: The behaviour might very well have come with the update to
mdadm-3.1.4, which may well have come nearly in parallel with me
updating the kernels... (as Gentoo stable jumped from 3.0 to 3.1.4 in
late October, at the beginning of November I updated the kernels...)

Am 03.12.2010 02:30, schrieb Neil Brown:
> On Thu, 2 Dec 2010 22:16:25 +0100 Mario 'BitKoenig' Holbe
> <Mario.Holbe@TU-Ilmenau.DE> wrote:
>
>> Stefan /*St0fF*/ Hübner <stefan.huebner@stud.tu-ilmenau.de> wrote:
>>> Now I have the effect that upon plugging in drives that formerly were
>>> part of an array, the md_mod modules gets loaded and tries to
>>> auto-assemble arrays.  This disturbs the diagnosis.
>>> I've tried raid=noautodetect as kernel commandline, and I grepped the
>>> source for the MODULE_PARM_DESC macro, which yielded no (useful) result.
>>>  This "automagic" behaviour happens since 2.6.36.
>> Are you sure this autodetection is triggered by the module?
>> And are you sure this behaviour is bound to this specific kernel
>> version?
>>
>> In-Kernel auto-assembly is usually not active when md is compiled as
>> module. Probably in your case this is some udev-triggered assembly?
> s/usually not/never/
>
> With a sufficiently recent mdadm, you can put
>    AUTO -all
>
> in mdadm.conf to disable auto-assembly.
>
> Alternately, find the udev rule (/lib/udev/rules.d/64-md-something) and 
> comment out the bit where it runs "mdadm -I" or "mdadm --incremental".
>
> NeilBrown
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-12-06 21:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 19:28 turn off auto assembly Stefan /*St0fF*/ Hübner
2010-12-02 21:16 ` Mario 'BitKoenig' Holbe
2010-12-03  1:24   ` Stefan Hübner
2010-12-03  1:30   ` Neil Brown
2010-12-06 21:52     ` Stefan Hübner [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=4CFD5B38.2090801@stud.tu-ilmenau.de \
    --to=stefan.huebner@stud.tu-ilmenau.de \
    --cc=Mario.Holbe@TU-Ilmenau.DE \
    --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).