From: Neil Brown <neilb@suse.de>
To: Sean Puttergill <puttergi@yahoo.ca>
Cc: dean gaudet <dean@arctic.org>, linux-raid@vger.kernel.org
Subject: Re: Auto-assembling arrays using mdadm
Date: Fri, 10 Mar 2006 16:28:56 +1100 [thread overview]
Message-ID: <17425.3736.352007.884424@cse.unsw.edu.au> (raw)
In-Reply-To: message from Sean Puttergill on Thursday March 9
On Thursday March 9, puttergi@yahoo.ca wrote:
It is not clear to me that this is something that you would ever want
to do, just as you would not want an automatic process to mount every
filesystem that it finds on any disk drive. (I agree with dean here).
Maybe if you explained why you wanted to do this, a more focussed
response could be provided.
> That did the trick, except you must do:
>
> mdadm --examine --scan --config=tmp.mdadm.conf
> >>tmp.mdadm.conf
>
> instead of:
>
> mdadm --detail --scan --config=tmp.mdadm.conf
> >>tmp.mdadm.conf
>
> I assume that this method would have the same problems
> with conflicting minor number. Will have to add an
> intermediate step to process the tmp.mdadm.conf file
> to uniquify the RAID array device names (i.e. remove
> duplicate /dev/md0, etc.).
>
>
> Thanks for the tip. I personally think mdadm should
> be modified to do this all in one step (including
> dealing with minor number conflicts).
This is unlikely to happen.
It is, however, possible that "mdadm --examine --scan" could grow an option
whereby the device names are given as
/dev/md/UUID:OF:THE:ARRAY:THAT:WAS:FOUND
This, toogether with giving 'auto=mdp' could avoid and issues with
minor number conflicts. Then:
echo DEV partitions > /etc/mdadm.conf
mdadm -Es --new-flag >> /etc/mdadm.conf
mdadm -As --auto-mdp
would assemble all arrays, which is what you claim to want.
NeilBrown
next prev parent reply other threads:[~2006-03-10 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 8:54 Auto-assembling arrays using mdadm Sean Puttergill
2006-03-09 17:41 ` dean gaudet
2006-03-09 19:23 ` Sean Puttergill
2006-03-09 21:51 ` dean gaudet
2006-03-10 4:58 ` Sean Puttergill
2006-03-10 5:28 ` Neil Brown [this message]
2006-03-10 9:34 ` Sean Puttergill
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=17425.3736.352007.884424@cse.unsw.edu.au \
--to=neilb@suse.de \
--cc=dean@arctic.org \
--cc=linux-raid@vger.kernel.org \
--cc=puttergi@yahoo.ca \
/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