linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <Paul.Clements@SteelEye.com>
To: Herta Van den Eynde <herta.vandeneynde@cc.kuleuven.ac.be>
Cc: linux-raid@vger.kernel.org
Subject: Re: what happens to raid when more disks are added?
Date: Wed, 07 May 2003 12:37:23 -0400	[thread overview]
Message-ID: <3EB93643.D55A2AD5@SteelEye.com> (raw)
In-Reply-To: 3EB929C3.6040400@cc.kuleuven.ac.be

Herta Van den Eynde wrote:
 
> To linux, they are known as devices sd[c-h], which have been configured
> as raid 0+1:
> 
> # cat /proc/mdstat
> Personalities : [raid0] [raid1]
> read_ahead 1024 sectors
> md2 : active raid1 md1[1] md0[0]
>       106679168 blocks [2/2] [UU]
> 
> md0 : active raid0 sde1[2] sdd1[1] sdc1[0]
>       106679232 blocks 8k chunks
> 
> md1 : active raid0 sdh1[2] sdg1[1] sdf1[0]
>       106679232 blocks 8k chunks
> 
> unused devices: <none>

It's generally thought to be better to set this up as a RAID 1+0 (three
raid1 devices striped together) but maybe there's a reason why you've
opted for the RAID 0+1? (there's one less md device, I guess)...

 
> When I need to add extra disks, e.g. in slots 3 and 12, I assume that
> the disk in slot 3 will get device name /dev/sdf, and the disks in slots
> 9 through 12 will subsequently be known as /dev/sd[g-j].  How will that
> affect the raid 0+1 config?

You may want to think about using the autodetection feature of md (or
mdadm's UUID capability)... these would allow you to avoid messing
things up if your drive letters shift on you...

--
Paul

  reply	other threads:[~2003-05-07 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 15:44 what happens to raid when more disks are added? Herta Van den Eynde
2003-05-07 16:37 ` Paul Clements [this message]
2003-05-08  8:10   ` Herta Van den Eynde

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=3EB93643.D55A2AD5@SteelEye.com \
    --to=paul.clements@steeleye.com \
    --cc=herta.vandeneynde@cc.kuleuven.ac.be \
    --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;
as well as URLs for NNTP newsgroup(s).