linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: "Joachim Otahal (privat)" <Jou@gmx.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 with two drive sizes question
Date: Tue, 5 Jun 2012 23:39:53 +0600	[thread overview]
Message-ID: <20120605233953.2086cc4c@natsu> (raw)
In-Reply-To: <4FCE4199.7030705@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

On Tue, 05 Jun 2012 19:27:53 +0200
"Joachim Otahal (privat)" <Jou@gmx.net> wrote:

> Hi,
> Debian 6.0.4 / superblock 1.2
> sdc1 = 1.5 TB
> sdd1 = 1.5 TB (cannot be used during --create, contains still data)
> sde1 = 1 TB
> sdf1 = 1 TB
> sdg1 = 1 TB
> 
> Target: RADI5 with 4.5 TB capacity.
> 
> The normal case would be:
> mdadm -C /dev/md3 --bitmap=internal -l 5 -n 5 /dev/sdc1 /dev/sdd1 
> /dev/sde1 /dev/sdf1 /dev/sdg1
> What I expect: since the first and the second drive are 1.5 TB size the 
> third fouth and fifth drive are treated like 2*1.5 TB, creating a 4.5 TB 
> RAID.

Lolwhat.

> What would really be created: I know here are people that know and not 
> guess : ).

5x1TB RAID5. Lowest common device size across all RAID members is utilized in
an array.

But what you do after that, is you also create a separate 2x0.5TB RAID1 from
the 1.5TB drives' "tails", and join both arrays into a single larger volume using LVM.

The result: 4.5 TB of usable space, with one-drive-loss tolerance (provided by
RAID5 in the first 4 TB, and by RAID1 in the 0.5TB "tail").

-- 
With respect,
Roman

~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-06-05 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 17:27 RAID5 with two drive sizes question Joachim Otahal (privat)
2012-06-05 17:39 ` Roman Mamedov [this message]
2012-06-05 19:41   ` Joachim Otahal (privat)
2012-06-05 19:59     ` Roman Mamedov
2012-06-05 20:36       ` Stan Hoeppner
2012-06-05 20:48         ` Joachim Otahal (privat)
2012-06-06  4:16         ` Roman Mamedov
2012-06-07  0:39           ` Stan Hoeppner

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=20120605233953.2086cc4c@natsu \
    --to=rm@romanrm.ru \
    --cc=Jou@gmx.net \
    --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).