linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lem <l3mming@iinet.net.au>
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: Wed, 13 Sep 2006 16:56:55 +1000	[thread overview]
Message-ID: <1158130615.4500.9.camel@localhost.localdomain> (raw)
In-Reply-To: <4507212E.3060703@maine.edu>

On Tue, 2006-09-12 at 17:05 -0400, Steve Cousins wrote:

> 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.

> 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.

From personal experience, partitions would be much easier. I've still
got an issue on my RAID5 where one of the hard disks has a bogus/fake
partition table on it (simply due to the data on the RAID appearing like
a partition table). It causes problems with lilo and other processes at
boot time (all non-fatal except for lilo). Perhaps with time I'll get
lucky and the data in that particular part of the drive will be changed
to something that looks nothing like a partition table :)


Lem.

      parent reply	other threads:[~2006-09-13  6:56 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
2006-09-13  6:56     ` Lem [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=1158130615.4500.9.camel@localhost.localdomain \
    --to=l3mming@iinet.net.au \
    --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).