From: Bill Davidsen <davidsen@tmr.com>
To: Steve Cousins <steve.cousins@maine.edu>
Cc: 'Neil Brown' <neilb@suse.de>,
'Linux RAID Mailing List' <linux-raid@vger.kernel.org>
Subject: Re: Correct way to create multiple RAID volumes with hot-spare?
Date: Sat, 16 Sep 2006 10:44:34 -0400 [thread overview]
Message-ID: <450C0DD2.2030506@tmr.com> (raw)
In-Reply-To: <4509849B.3020006@maine.edu>
Steve Cousins wrote:
>
>
> Ruth Ivimey-Cook wrote:
>
>> Steve,
>>
>>> The recent "Messed up creating new array..." thread has someone who
>>> started by using the whole drives but she now wants to use
>>> partitions because the array is not starting automatically on boot
>>> (I think that was the symptom). I'm guessing this is because there
>>> is no partigion ID of "fd" since there isn't even a partition.
>>
>>
>>
>> Yes, that's right.
>
>
> Thanks Ruth.
>
>
> Neil (or others), what is the recommended way to have the array start
> up if you use whole drives instead of partitions? Do you put mdadm -A
> etc. in rc.local?
I think you want it earlier than that, unless you want to do the whole
mounting process by hand. It's distribution dependent, but doing it
early allows the array to be handled like any other block device.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-09-16 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 19:05 Correct way to create multiple RAID volumes with hot-spare? Steve Cousins
2006-08-23 10:34 ` Justin Piszcz
2006-08-23 13:17 ` Joshua Baker-LePain
2006-08-25 16:17 ` Steve Cousins
2006-08-23 22:42 ` Neil Brown
2006-08-25 17:10 ` Steve Cousins
2006-09-12 21:05 ` Steve Cousins
2006-09-12 22:25 ` Ruth Ivimey-Cook
2006-09-14 16:34 ` Steve Cousins
2006-09-14 16:58 ` Neil Brown
2006-09-16 14:44 ` Bill Davidsen [this message]
2006-09-13 6:56 ` Lem
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=450C0DD2.2030506@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=steve.cousins@maine.edu \
/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).