From: Sean Puttergill <puttergi@yahoo.ca>
To: dean gaudet <dean@arctic.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Auto-assembling arrays using mdadm
Date: Thu, 9 Mar 2006 23:58:49 -0500 (EST) [thread overview]
Message-ID: <20060310045849.65628.qmail@web35304.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0603091344010.32502@twinlark.arctic.org>
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).
Sean
--- dean gaudet <dean@arctic.org> wrote:
> you know i've been bitten by that several times...
> the kernel sees the
> autodetect partition type of a disk which used to
> belong in another box
> (which for various reasons i've not yet been able to
> zero the old raid
> superblock)... and brings up a raid minor which
> conflicts with another
> array already present in the system... which causes
> device renaming to
> occur and can mess up the boot. (although if i'm
> using UUIDs or labels
> for mounting the filesystems it can almost work --
> there are still a few
> cases where those don't help... such as xfs external
> log partition.)
>
> i suppose what i suggested doesn't do what you
> want... but i prefer not
> using kernel autoassembly these days because of the
> above problem.
>
> the 1.12 man page has more examples which can help
> you...
>
> echo "DEVICE partitions" >tmp.mdadm.conf
> mdadm --detail --scan --config=tmp.mdadm.conf
> >>tmp.mdadm.conf
> mdadm --assemble --scan --config=tmp.mdadm.conf
>
> i think that'll do what you want...
>
> -dean
> -
> 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
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-03-10 4:58 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 [this message]
2006-03-10 5:28 ` Neil Brown
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=20060310045849.65628.qmail@web35304.mail.mud.yahoo.com \
--to=puttergi@yahoo.ca \
--cc=dean@arctic.org \
--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