Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: The performance is not as expected when used several disks on raid0.
Date: Mon, 17 Aug 2015 07:38:13 -0400	[thread overview]
Message-ID: <55D1C7A5.7050204@gmail.com> (raw)
In-Reply-To: <pan$82931$bcf5ef1b$88d8d18$c8aa5770@cox.net>

[-- Attachment #1: Type: text/plain, Size: 2776 bytes --]

On 2015-08-15 02:30, Duncan wrote:
> Austin S Hemmelgarn posted on Fri, 14 Aug 2015 15:58:30 -0400 as
> excerpted:
>
>> FWIW, running BTRFS on top of MDRAID actually works very well,
>> especially for BTRFS raid1 on top of MD-RAID0 (I get an almost 50%
>> performance increase for this usage over BTRFS raid10, although most of
>> this is probably due to how btrfs dispatches I/O's to disks in
>> multi-disk stetups).
>
> Of course that's effectively a raid01, which is normally supposed to most
> often be a mistakenly reversed raid10 implementation, mistakenly, due to
> the IO cost of the rebuild should a device fail, since the whole raid0 of
> the one raid1 side would have to be rereplicated to the other, vs only
> having to rereplicate one device to the other locally, in a raid10
> arrangement.
>
> However, in this case it's a very smart arrangement, actually, the only
> md-raid-under-btrfs-raid arrangement that makes real sense (well, other
> than raid00, raid0 at both levels, perhaps), in particular because the
> btrfs raid1 on top still gives you the full benefit of btrfs file
> integrity features as well as the usual raid1 redundancy, tho in this
> case it's only at the one raid0 against the other as the pair of btrfs
> raid1 copies.  And the mdraid0 is much better optimized than btrfs raid0,
> so there's that bonus, while at the same time the btrfs raid1 redundancy
> nicely balances the usual "Russian Roulette" quality of raid0.
>
> Very nice configuration! =:^)
>
> Thanks for mentioning it, as I guess I was effectively ruling it out as
> an option before even really considering it due to the usual raid10's
> better than raid01 thing, and thus was entirely blind to the
> possibility.  Which was bad, because as I alluded to, mdraid's lack of
> file integrity features and thus lack of any way to have btrfs scrub
> properly filter down to the mdraid level when there's mdraid level
> redundancy, kind of makes a mess of things, otherwise.  But btrfs raid1
> on mdraid0 effectively balances and eliminates the negatives at each
> level with the strengths of the other level, and is really a quite
> awesome solution, that until now I was entirely blinded to! =:^)
>
I've also found that BTRFS raid5/6 on top of MD RAID0 mitigates (to a 
certain extent that is) the performance penalty of doing raid5/6 if you 
aren't on ridiculously fast storage, probably not something that should 
be used in production yet, but it's how I've got the near-line backups 
setup on my home server system.  It may also be worth pointing out that 
BTRFS raid6 lets you use 4 disks minimum, as opposed to most other raid6 
implementations that (unnecessarily, as a 4 disk RAID6 is not a 
degenerate form) require 5.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]

  reply	other threads:[~2015-08-17 11:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 15:16 The performance is not as expected when used several disks on raid0 Eduardo Bach
2015-08-14 16:30 ` Calvin Walton
2015-08-14 16:35   ` Calvin Walton
2015-08-17 19:44     ` Eduardo Bach
2015-08-17 20:36       ` Calvin Walton
2015-08-14 18:31 ` Chris Murphy
2015-08-14 19:50   ` Austin S Hemmelgarn
2015-08-14 19:54     ` Chris Murphy
2015-08-14 19:58       ` Austin S Hemmelgarn
2015-08-15  6:30         ` Duncan
2015-08-17 11:38           ` Austin S Hemmelgarn [this message]
2015-08-17 23:06             ` Duncan
2015-08-18 11:34               ` Austin S Hemmelgarn
2015-08-18 14:59                 ` Duncan
2015-08-17 19:57   ` Eduardo Bach

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=55D1C7A5.7050204@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=1i5t5.duncan@cox.net \
    --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