From: Sean Puttergill <puttergi@yahoo.ca>
To: Neil Brown <neilb@suse.de>
Cc: dean gaudet <dean@arctic.org>, linux-raid@vger.kernel.org
Subject: Re: Auto-assembling arrays using mdadm
Date: Fri, 10 Mar 2006 04:34:58 -0500 (EST) [thread overview]
Message-ID: <20060310093459.67755.qmail@web35304.mail.mud.yahoo.com> (raw)
In-Reply-To: <17425.3736.352007.884424@cse.unsw.edu.au>
I definitely wish to do this, that's why I'm asking.
I assume your statement refers to the general
usefulness of what I am asking for.
As to why I wish to implement this functionality, well
you can tell that I am not targetting this at your
average user's PC. Not to be too secretive, but think
along the lines of something more appliance like.
Amongst the requirements that I have for the system
that I am constructing, I must deal with installing
RAID sets that come from other boxes. I need to be
able to automatically start up existing RAID arrays on
drive sets that have migrated over without needing to
have any a priori knowledge of the RAID arrays that
might exist on the drives.
In any case, your suggestion of a new flag to output
unique device names from mdadm --examine (using UUID
of array) sounds like an acceptable solution. Please
consider adding it.
I assume that using "--auto=md" when assembling will
currently not take care of minor number conflicts in
the config file?
Thanks,
Sean
--- Neil Brown <neilb@suse.de> wrote:
> 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
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
prev parent reply other threads:[~2006-03-10 9:34 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
2006-03-10 9:34 ` Sean Puttergill [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=20060310093459.67755.qmail@web35304.mail.mud.yahoo.com \
--to=puttergi@yahoo.ca \
--cc=dean@arctic.org \
--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