From: seth vidal <skvidal@phy.duke.edu>
To: Hermann Himmelbauer <dusty@strike.wu-wien.ac.at>
Cc: Dan Egli <dan@eglifamily.dnsalias.net>, linux-raid@vger.kernel.org
Subject: Re: raid 0 on different size devices?
Date: 19 Nov 2003 14:22:21 -0500 [thread overview]
Message-ID: <1069269741.6952.33.camel@opus> (raw)
In-Reply-To: <200311192018.14555.dusty@strike.wu-wien.ac.at>
> AFAIK they have to be of equal size but as you can create a 27GB partition on
> the 40GB drive, you could at least get 54GB out of this configuration.
No. I have a 120GB and a 60GB disk in a linear array working just fine.
it's not technically raid0, but it lets the person do what they're
wanting to do.
-sv
next prev parent reply other threads:[~2003-11-19 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 18:57 raid 0 on different size devices? Dan Egli
2003-11-19 19:00 ` seth vidal
2003-11-19 19:18 ` Hermann Himmelbauer
2003-11-19 19:22 ` seth vidal [this message]
2003-11-19 20:01 ` Dan Egli
2003-11-19 20:05 ` seth vidal
2003-11-19 20:21 ` Jose Luis Domingo Lopez
2003-11-19 23:51 ` Neil Brown
2003-11-19 19:24 ` Mike Dresser
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=1069269741.6952.33.camel@opus \
--to=skvidal@phy.duke.edu \
--cc=dan@eglifamily.dnsalias.net \
--cc=dusty@strike.wu-wien.ac.at \
--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