Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Phillip Susi <phill@thesusis.net>
To: George Shammas <btrfs@shamm.as>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: What exactly is BTRFS Raid 10?
Date: Fri, 19 Aug 2022 14:10:24 -0400	[thread overview]
Message-ID: <87v8qokryt.fsf@vps.thesusis.net> (raw)
In-Reply-To: <a3fc9d94-4539-429a-b10f-105aa1fd3cf3@www.fastmail.com>


"George Shammas" <btrfs@shamm.as> writes:

> Hello,
>
>  I've been searching and reading docs for a few days now, and btrfs raid 10 is a mystery to me. 
>
> This is mostly a documentation question, as many places reference it
> but nothing actually describes it and the real question is how does it
> differ from btrfs raid1.
>
> Both BTRFS Raid1 and Raid10 
>  - Allows arbitrary number of drives (>=2), including odd numbers. 
>  - Will write duplicate blocks across disks.

Btrfs raid10 requires an even number of drives with a minimum of 4.
It's pretty much raid 1+0.


> https://btrfs.readthedocs.io/en/latest/mkfs.btrfs.html?highlight=raid10#profile-layout
>
> The Raid 1 example there also likely needs a bit of explanation or
> validation, as all the blocks are written to one device. In that raid
> one example three devices could be lost as long as it is not one of
> them is the first device. It also cannot be accurate once the amount
> stored is above 1 full drive.

It is meant to show a *possible* layout, not every potential layout.
The data may be stored like than and then yes, you could lose multiple
drives and still recover as long as the lost drives were 2, 3, and 4.


  reply	other threads:[~2022-08-19 18:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 16:49 What exactly is BTRFS Raid 10? George Shammas
2022-08-19 18:10 ` Phillip Susi [this message]
2022-08-19 22:01   ` George Shammas
2022-08-19 22:18     ` Chris Murphy
2022-08-19 22:37       ` George Shammas
2022-08-19 22:29     ` waxhead
2022-08-22 19:51     ` Phillip Susi
2022-08-20 11:28 ` Goffredo Baroncelli
2022-08-20 18:11   ` Andrei Borzenkov
2022-08-21  0:23     ` Qu Wenruo

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=87v8qokryt.fsf@vps.thesusis.net \
    --to=phill@thesusis.net \
    --cc=btrfs@shamm.as \
    --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