From: Bob McElrath <bob@mcelrath.org>
To: Roman Mamedov <rm@romanrm.ru>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: heterogeneous raid1
Date: Fri, 23 Mar 2012 16:49:32 +0000 [thread overview]
Message-ID: <20120323164932.GB11099@mcelrath.org> (raw)
In-Reply-To: <20120323164435.4c21f92e@natsu>
Roman Mamedov [rm@romanrm.ru] wrote:
> 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.
The algorithm I proposed wastes a lot less space. The above article wastes 2Tb
in his first example, while mine would waste 0 in a raid1. (2Tb+1Tb+1Tb) and
4Tb in raid1.
And I've chosen not to worry about 2-disk failures.
> 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/
I'm aware of that, and decided against it. The way btrfs does things is the way
of the future. Using multiple raids there are so many layers (md+md+lvm+btrfs)
that it becomes an administration nightmare, and I've had enough of rebuilding
raid arrays by hand for one lifetime.
--
Cheers, Bob McElrath
"The individual has always had to struggle to keep from being overwhelmed by
the tribe. If you try it, you will be lonely often, and sometimes frightened.
But no price is too high to pay for the privilege of owning yourself."
-- Friedrich Nietzsche
next prev parent reply other threads:[~2012-03-23 16:49 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
2012-03-23 16:49 ` Bob McElrath [this message]
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=20120323164932.GB11099@mcelrath.org \
--to=bob@mcelrath.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.ru \
/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