linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ruth Ivimey-Cook" <Ruth.Ivimey-Cook@ivimey.org>
To: 'Steve Cousins' <steve.cousins@maine.edu>, 'Neil Brown' <neilb@suse.de>
Cc: 'Linux RAID Mailing List' <linux-raid@vger.kernel.org>
Subject: RE: Correct way to create multiple RAID volumes with hot-spare?
Date: Tue, 12 Sep 2006 23:25:12 +0100	[thread overview]
Message-ID: <000001c6d6ba$50819ad0$0e00a8c0@sherlock> (raw)
In-Reply-To: <4507212E.3060703@maine.edu>

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.

> I'm on the verge of re-doing this array with 11 full drives 
> (/dev/sd? as opposed to /dev/sd?1 and /dev/sd?2).  Will I 
> have the same problems with booting?  I like the idea of not 
> having to partition the drives but not if it is going to 
> cause hassles.  I realize that there could be a potential 
> problem if I need to replace a drive with a slightly 
> different model that is slightly smaller.

That's the reason I ended up re-creating the array from backup, using
partitions.

You _can_ use raw disks, but it's not as easy. I worked out that I was
originally having problems because my mdadm.conf file had the right drives
(/dev/sdc ...) in the ARRAY line, but didn't have the same drives listed in the
DEVICES line.

I would suggest you do use partitions.

Ruth


  reply	other threads:[~2006-09-12 22:25 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 [this message]
2006-09-14 16:34       ` Steve Cousins
2006-09-14 16:58         ` Neil Brown
2006-09-16 14:44         ` Bill Davidsen
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='000001c6d6ba$50819ad0$0e00a8c0@sherlock' \
    --to=ruth.ivimey-cook@ivimey.org \
    --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).