From: David Greaves <david@dgreaves.com>
To: Dexter Filmore <Dexter.Filmore@gmx.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: --no-degraded in mdadm.conf? / disable auto assembly
Date: Tue, 29 Apr 2008 14:02:47 +0100 [thread overview]
Message-ID: <48171C77.3080206@dgreaves.com> (raw)
In-Reply-To: <200804291355.59052.Dexter.Filmore@gmx.de>
Dexter Filmore wrote:
> How do I prevent mdadm from assembling any array at all without uninstalling
> the package? I commented out all lines, still it seems it scanned and
> assembled what it found.
> (Possibly a debian thing, will look into this)
AFAIK there are 3 places where an array is assembled 'automatically'
1. kernel auto-detect of 0xfd partitions - not mdadm, not currently preventable
AFAIK.
2. initrd mdadm script
3. init.d mdadm script
I'm not sure how udev figures into this... ISTR that some distros had udev
script issues when udev detected and assembled an array when it had found
'enough' components and then triggered a resync when the final component popped up.
> Next thing: I don't want mdadm to assemble arrays if not all disks are
> present. Can I pass no-degraded to mdadm.conf?
Yes. man madadm:
--no-degraded
This is the reverse of --run in that it inhibits the started if
array unless all expected drives are present. This
is only needed with --scan and can be used if you physical
connections to devices are not as reliable as you would
like.
Of course it may be in a newer version :)
Where's the git page for mdadm then?
> Is there a dry-run-option that says what would happen if I assembled now?
Not AFAIK - plus, I think this would be an md function wouldn't it? Doesn't
mdadm just ask the kernel md module to assemble the components without checking
event counts etc.
David
next prev parent reply other threads:[~2008-04-29 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 11:55 --no-degraded in mdadm.conf? / disable auto assembly Dexter Filmore
2008-04-29 13:02 ` David Greaves [this message]
2008-04-29 13:07 ` David Greaves
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=48171C77.3080206@dgreaves.com \
--to=david@dgreaves.com \
--cc=Dexter.Filmore@gmx.de \
--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 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).