linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ashford@whisperpc.com
To: "Phillip Susi" <psusi@ubuntu.com>,
	"Jose Manuel Perez Bethencourt" <jmperezbeth@gmail.com>
Cc: ashford@whisperpc.com, "Chris Murphy" <lists@colorremedies.com>,
	"sys.syphus" <syssyphus@gmail.com>,
	"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: I need to P. are we almost there yet?
Date: Tue, 30 Dec 2014 15:17:17 -0800	[thread overview]
Message-ID: <40b56c60ddd4801295a92c4b11d5c08e.squirrel@webmail.wanet.net> (raw)
In-Reply-To: <54A31CAE.4020606@ubuntu.com>

> Phillip Susi wrote:
>
>> I'm wondering which of the above the BTRFS implementation most
>> closely resembles.
>
> Unfortunately, btrfs just uses the naive raid1+0, so no 2 or 3 disk
> raid10 arrays, and no higher performing offset layout.

> Jose Manuel Perez Bethencourt wrote:
>
> I think you are missing crucial info on the layout on disk that BTRFS
> implements. While a traditional RAID1 has a rigid layout that has
> fixed and easily predictable locations for all data (exactly on two
> specific disks), BTRFS allocs chunks as needed on ANY two disks.
> Please research into this to understand the problem fully, this is the
> key to your question.

There is a HUGE difference here.  In the first case, the data will have a
>50% chance of surviving a 2-drive failure.  In the second case, the data
will have an effectively 0% chance of surviving a 2-drive failure.  I
don't believe I need to mention which of the above is more reliable, or
which I would prefer.

I believe that someone who understands the code in depth (and that may
also be one of the people above) determine exactly how BTRFS implements
RAID-10.

Thank you.

Peter Ashford


  reply	other threads:[~2014-12-30 23:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 18:56 I need to P. are we almost there yet? sys.syphus
2014-12-29 19:00 ` sys.syphus
2014-12-29 19:04   ` Hugo Mills
2014-12-29 20:25     ` sys.syphus
2014-12-29 21:50       ` Hugo Mills
2014-12-29 21:16   ` Chris Murphy
2014-12-30  0:20     ` ashford
     [not found]       ` <CALBWd85UsSih24RhwpmDeMjuMWCKj9dGeuZes5POj6qEFkiz2w@mail.gmail.com>
2014-12-30 17:09         ` Fwd: " Jose Manuel Perez Bethencourt
2014-12-30 21:44       ` Phillip Susi
2014-12-30 23:17         ` ashford [this message]
2014-12-31  2:45           ` Phillip Susi
2014-12-31 17:27             ` ashford
2014-12-31 23:38               ` Phillip Susi
2015-01-01  1:26               ` Chris Samuel
2015-01-01 20:12                 ` Roger Binns
2015-01-02  3:47                   ` Duncan
2015-01-02 13:42               ` Austin S Hemmelgarn
2015-01-02 17:45                 ` Brendan Hide
2015-01-02 19:41                   ` Austin S Hemmelgarn
2014-12-29 21:13 ` Chris Murphy
2015-01-03 11:34 ` Bob Marley
2015-01-03 13:11   ` Duncan
2015-01-03 18:53     ` Bob Marley
2015-01-03 19:03       ` sys.syphus
2015-01-03 18:55     ` sys.syphus
2015-01-04  3:22       ` Duncan
2015-01-04  3:54         ` Hugo Mills
2015-01-03 21:58     ` Roman Mamedov
2015-01-04  3:24       ` Duncan

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=40b56c60ddd4801295a92c4b11d5c08e.squirrel@webmail.wanet.net \
    --to=ashford@whisperpc.com \
    --cc=jmperezbeth@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=psusi@ubuntu.com \
    --cc=syssyphus@gmail.com \
    /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).