linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Davis <alex14641@yahoo.com>
To: Richard Michael <rmichael-raid@edgeofthenet.org>,
	Kasper Sandberg <lkml@metanurb.dk>,
	Helge Hafting <helge.hafting@aitel.hist.no>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Sharing disks amoung multiple software RAIDs
Date: Fri, 2 May 2008 07:13:45 -0700 (PDT)	[thread overview]
Message-ID: <271684.86609.qm@web50210.mail.re2.yahoo.com> (raw)
In-Reply-To: <481B1A7D.2020000@aitel.hist.no>

> > > Can you explain what you mean, exactly?
> > As an example, you have disks /dev/sd[abc]. /dev/md0 would be made 
> > from /dev/sda1, /dev/sdb1, and /dev/sdc1; /dev/md1 would be made
> > from /dev/sda2, /dev/sdb2, and /dev/sdc2.

> I've been watching this thread with interest, because I wanted
> clarification on what the OP meant.

> If by "sharing disks", the OP meant the above, I'm surprised (and
>  concerned) there's any question at all.  How is this anything other    > than the definition of "mirror"? 
md0 and md1 are both RAID 5 arrays, not mirrors.



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

  reply	other threads:[~2008-05-02 14:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01 11:35 Sharing disks amoung multiple software RAIDs Alex Davis
2008-05-01 12:50 ` Justin Piszcz
2008-05-01 13:42   ` Alex Davis
2008-05-02 21:24     ` Bill Davidsen
2008-05-02  1:39   ` Kasper Sandberg
2008-05-02  1:51     ` Alex Davis
2008-05-02  2:31       ` David Lethe
2008-05-02  2:42         ` Kasper Sandberg
2008-05-02  7:06           ` David Rees
2008-05-02  8:09             ` Kasper Sandberg
2008-05-02  8:25               ` David Greaves
2008-05-02 21:43                 ` Kasper Sandberg
2008-05-02 22:04                   ` Alex Davis
2008-05-02 22:24                   ` David Lethe
2008-05-03  0:44                     ` Alex Davis
2008-05-03 10:13                       ` Keld Jørn Simonsen
2008-05-03  3:11                     ` Kasper Sandberg
2008-05-02 10:25               ` Keld Jørn Simonsen
     [not found]                 ` <481E0726.1030501@harddata.com>
     [not found]                   ` <20080504212927.GB20650@rap.rap.dk>
     [not found]                     ` <481E3374.4070105@harddata.com>
2008-05-04 23:10                       ` Keld Jørn Simonsen
2008-05-04 23:17                         ` Keld Jørn Simonsen
2008-05-02 13:43               ` Helge Hafting
2008-05-02 14:13                 ` Alex Davis [this message]
2008-05-01 12:51 ` David Greaves
2008-05-02  1:23 ` Nick Andrew
  -- strict thread matches above, loose matches on Subject: below --
2008-05-02  8:36 George Spelvin
2008-05-02 11:07 ` Alex Davis
2008-05-02 13:26   ` Richard Michael

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=271684.86609.qm@web50210.mail.re2.yahoo.com \
    --to=alex14641@yahoo.com \
    --cc=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=lkml@metanurb.dk \
    --cc=rmichael-raid@edgeofthenet.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).