From: Roman Mamedov <rm@romanrm.ru>
To: Bob McElrath <bob@mcelrath.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: heterogeneous raid1
Date: Fri, 23 Mar 2012 16:44:35 +0600 [thread overview]
Message-ID: <20120323164435.4c21f92e@natsu> (raw)
In-Reply-To: <20120323061159.GA11099@mcelrath.org>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
On Fri, 23 Mar 2012 06:11:59 +0000
Bob McElrath <bob@mcelrath.org> wrote:
> http://superuser.com/questions/387851/a-zfs-or-lvm-or-md-redundant-heterogeneous-storage-proposal/388536
>
> In a nutshell: organize your heterogenous disks into two "halves", the sum of
> which are of roughly equal size, and create a raid1 array across those two
> halves.
This seems to be an extremely simplistic concept and also a very inefficient
use of storage space, while not even providing enough redundancy (can't
reliably tolerate an any-two-disks failure even).
I suggest that you go with http://linuxconfig.org/prouhd-raid-for-the-end-user
instead. Depending on how many drives you have, the widest portion can be raid
6, then decreasing to RAID5 for the second stage, then finally to RAID1 for
the tail.
Also remember that with MD you can also create arrays from arrays. So e.g. a
RAID0 of two 500GB members can join a RAID6 of 1TB members. More on this idea:
http://louwrentius.com/blog/2008/08/building-a-raid-6-array-of-mixed-drives/
--
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 --]
next prev parent reply other threads:[~2012-03-23 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 6:11 heterogeneous raid1 Bob McElrath
2012-03-23 6:47 ` cwillu
2012-03-23 10:20 ` Hugo Mills
2012-03-24 7:15 ` Duncan
2012-03-23 10:44 ` Roman Mamedov [this message]
2012-03-23 16:49 ` Bob McElrath
2012-03-23 17:13 ` Roman Mamedov
2012-03-23 17:35 ` Bob McElrath
2012-03-25 11:48 ` Chris Samuel
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=20120323164435.4c21f92e@natsu \
--to=rm@romanrm.ru \
--cc=bob@mcelrath.org \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.