From: Neil Brown <neilb@suse.de>
To: "Patrick H." <linux-raid@feystorm.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: disable creation of md127
Date: Sat, 11 Dec 2010 13:44:06 +1100 [thread overview]
Message-ID: <20101211134406.35b91663@notabene.brown> (raw)
In-Reply-To: <4D02AB51.5090707@feystorm.net>
On Fri, 10 Dec 2010 15:36:01 -0700 "Patrick H." <linux-raid@feystorm.net>
wrote:
> Sent: Fri Dec 10 2010 14:58:59 GMT-0700 (Mountain Standard Time)
> From: Neil Brown <neilb@suse.de>
> To: Patrick H. <linux-raid@feystorm.net> linux-raid@vger.kernel.org
> Subject: Re: disable creation of md127
> > On Fri, 10 Dec 2010 14:38:30 -0700 "Patrick H." <linux-raid@feystorm.net>
> > wrote:
> >
> >
> >> How can I prevent the MD driver from auto-creating md127 on boot?
> >> I have a server which is exporting /dev/sdb1 via iSCSI. The remote
> >> client for this device is using it in a raid device so it has raid
> >> metadata on it. However because of this, when the target server boots
> >> up, the md driver shoves it into md127. And because of this, the iSCSI
> >> target daemon (tgtd) wont export the device as its now part of a raid
> >> device.
> >> The partition type is 0x83, not 0xfd.
> >>
> >> RHEL6 2.6.32-71
> >>
> >
> > The md driver isn't auto-creating this.
> > mdadm is being run and being asked to create this, possibly implicitly.
> >
> > Exactly how you stop this from happening depends on where it is an initrd
> > script or a boot script that is doing it, and which version of mdadm you have.
> >
> > If you have 3.0 or later, then putting
> > AUTO -all
> >
> > in mdadm.conf might be enough.
> > If you have a 2.x, you probably need to tell the init script not to run
> > mdadm, maybe edit the script, maybe set some default variable. I know little
> > about RHEL and so cannot suggest specifics.
> >
> > 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
> >
> Youre right. I removed every single md-related init script so I didnt
> think mdadm was doing it. But apparently I forgot about udev. I replaced
> mdadm with a script to dump out a bunch of info and found that udev is
> calling `mdadm -I /dev/sdb1`. Any idea where this might be configured
> at? I did a recursive grep for 'mdadm' in the entire /etc and found
> nothing but init scripts and a little selinux stuff (nothing in /etc/udev).
/lib/udev/rules.d/64-...something
You can disable this by creating an empty file with the same name
in /etc/udev/rules.d ... which might be kinder to the package management
system.
NeilBrown
prev parent reply other threads:[~2010-12-11 2:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 21:38 disable creation of md127 Patrick H.
2010-12-10 21:58 ` Neil Brown
2010-12-10 22:36 ` Patrick H.
2010-12-10 22:43 ` Patrick H.
2010-12-11 2:44 ` Neil Brown [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=20101211134406.35b91663@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@feystorm.net \
--cc=linux-raid@vger.kernel.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 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.