mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Brown <neilb@cse.unsw.edu.au>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problems with raid in 2.6.9-rc1-mm4
Date: Tue, 14 Sep 2004 11:13:45 +1000	[thread overview]
Message-ID: <16710.17865.374399.841645@cse.unsw.edu.au> (raw)
In-Reply-To: message from J.A. Magallon on Monday September 13

On Monday September 13, jamagallon@able.es wrote:
...
> As disks are of different sizes, I though about doing a volume with the small
> ones, and then a raid with the big.
> As stripping on two IDE disks on the same IDE bus is silly, I wanted to
> do a linear array. So this is what I would like:
> 
> /dev/md1 (raid0) -- /dev/hda1 (240Gb)
>                 \- /dev/md0 (raid linear) -- /dev/hdc1
>                                           \- /dev/hdd1
> 
....
> 
> What is the problem ? The kernel can't detect that md0 is part of an
> array ?

No, it cannot.

> Is this setup possible at all ?

Yes.  But don't use "autodetect" to start the array.  
Use "mdadm".   It is more flexible.

Or even, just use raid0 across all 3 drives.  raid0 copes quite
happily with drives of different sizes.

> Do I have to partition md0 and create a 'fd' partition ?

It might work, but I wouldn't suggest it.

> 
> Aside, I have thogut of this a a possible solution: split hda in two, and buid
> a raid0 with hda1,hdc1,hda2,hdd1 (hda is faster...). Is this so stupid as it
> looks to me (think of rplacinf hda2 when it fails....).

This would not be a clever idea for performance reasons.

If any drive fails you have lost all your data and will need to
restore from backups, so the possibility that hda2 dies is not
particularly interesting.

NeilBrown


      reply	other threads:[~2004-09-14  1:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 12:27 J.A. Magallon
2004-09-14  1:13 ` Neil Brown [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=16710.17865.374399.841645@cse.unsw.edu.au \
    --to=neilb@cse.unsw.edu.au \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®