From: Psalle <psalleetsile@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: raid1 vs raid5
Date: Wed, 20 Jan 2016 15:17:45 +0100 [thread overview]
Message-ID: <569F9709.4090608@gmail.com> (raw)
In-Reply-To: <568BEE3F.4060402@gmail.com>
I had forgotten about this post and on rethinking about it I realized
the kind of brain fart I was having. So thanks for the merciful silence ;-)
On 05/01/16 17:24, Psalle wrote:
> Hello all and excuse me if this is a silly question. I looked around
> in the wiki and list archives but couldn't find any in-depth
> discussion about this:
>
> I just realized that, since raid1 in btrfs is special (meaning only
> two copies in different devices), the effect in terms of resilience
> achieved with raid1 and raid5 are the same: you can lose one drive and
> not lose data.
>
> So!, presuming that raid5 were at the same level of maturity, what
> would be the pros/cons of each mode?
>
> As a corollary, I guess that if raid1 is considered a good compromise,
> then functional equivalents to raid6 and beyond could simply be
> implemented as "storing n copies in different devices", dropping any
> complex parity computations and making this mode entirely generic.
> Since this seems pretty obvious, I'd welcome your insights on what are
> the things I'm missing, since it doesn't exist (and it isn't planned
> to be this way, AFAIK). I can foresee consistency difficulties, but
> that seems hardly insurmountable if its being done for raid1?
>
> Thanks in advance,
> Psalle.
prev parent reply other threads:[~2016-01-20 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 16:24 raid1 vs raid5 Psalle
2016-01-06 8:09 ` Sean Greenslade
2016-01-20 14:17 ` Psalle [this message]
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=569F9709.4090608@gmail.com \
--to=psalleetsile@gmail.com \
--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 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).