From: Martin <rc6encrypted@gmail.com>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Recommended why to use btrfs for production?
Date: Fri, 3 Jun 2016 16:39:00 +0200 [thread overview]
Message-ID: <CAGQ70YcgHWDdXv785a5wwJqCPnJBscpDR3ASchTX5gpBnYKmvA@mail.gmail.com> (raw)
In-Reply-To: <dd952b29-1bea-59e1-1857-418b86951b47@gmail.com>
> I would say it is, but I also don't have quite as much experience with it as
> with BTRFS raid1 mode. The one thing I do know for certain about it is that
> even if it theoretically could recover from two failed disks (ie, if they're
> from different positions in the striping of each mirror), there is no code
> to actually do so, so make sure you replace any failed disks as soon as
> possible (or at least balance the array so that you don't have a missing
> device anymore).
Ok, so that really speaks for raid1...
> Most of my systems where I would run raid10 mode are set up as BTRFS raid1
> on top of two LVM based RAID0 volumes, as this gets measurably better
> performance than BTRFS raid10 mode at the moment (I see roughly a 10-20%
> difference on my home server system), and provides the same data safety
> guarantees as well. It's worth noting for such a setup that the current
> default block size in BTRFS is 16k except on very small filesystems, so you
> may want a larger stripe size than you would on a traditional filesystem.
>
> As far as BTRFS raid10 mode in general, there are a few things that are
> important to remember about it:
> 1. It stores exactly two copies of everything, any extra disks just add to
> the stripe length on each copy.
> 2. Because each stripe has the same number of disks as it's mirrored
> partner, the total number of disks in any chunk allocation will always be
> even, which means that if your using an odd number of disks, there will
> always be one left out of every chunk. This has limited impact on actual
> performance usually, but can cause confusing results if you have differently
> sized disks.
> 3. BTRFS (whether using raid10, raid0, or even raid5/6) will always try to
> use as many devices as possible for a stripe. As a result of this, the
> moment you add a new disk, the total length of all new stripes will adjust
> to fit the new configuration. If you want maximal performance when adding
> new disks, make sure to balance the rest of the filesystem afterwards,
> otherwise any existing stripes will just stay the same size.
Those are very good things to know!
next prev parent reply other threads:[~2016-06-03 14:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 9:49 Recommended why to use btrfs for production? Martin
2016-06-03 9:53 ` Marc Haber
2016-06-03 9:57 ` Martin
2016-06-03 10:01 ` Hans van Kranenburg
2016-06-03 10:15 ` Martin
2016-06-03 12:55 ` Austin S. Hemmelgarn
2016-06-03 13:31 ` Martin
2016-06-03 13:47 ` Julian Taylor
2016-06-03 14:21 ` Austin S. Hemmelgarn
2016-06-03 14:39 ` Martin [this message]
2016-06-03 19:09 ` Christoph Anton Mitterer
2016-06-09 6:16 ` Duncan
2016-06-09 11:38 ` Austin S. Hemmelgarn
2016-06-09 17:39 ` Chris Murphy
2016-06-09 19:57 ` Duncan
2016-06-03 14:05 ` Chris Murphy
2016-06-03 14:11 ` Martin
2016-06-03 15:33 ` Austin S. Hemmelgarn
2016-06-04 0:48 ` Nicholas D Steeves
2016-06-04 1:48 ` Chris Murphy
2016-06-06 13:29 ` Austin S. Hemmelgarn
2016-06-04 1:34 ` Chris Murphy
2016-06-05 10:45 ` Mladen Milinkovic
2016-06-05 16:33 ` James Johnston
2016-06-05 18:20 ` Andrei Borzenkov
2016-06-06 1:47 ` Chris Murphy
2016-06-06 2:40 ` James Johnston
2016-06-06 13:36 ` Austin S. Hemmelgarn
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=CAGQ70YcgHWDdXv785a5wwJqCPnJBscpDR3ASchTX5gpBnYKmvA@mail.gmail.com \
--to=rc6encrypted@gmail.com \
--cc=ahferroin7@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).