From: Roman Mamedov <rm@romanrm.net>
To: M G Berberich <btrfs@oss.m-berberich.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Questions on using BtrFS for fileserver
Date: Wed, 20 Aug 2014 03:50:38 +0600 [thread overview]
Message-ID: <20140820035038.40d09071@natsu> (raw)
In-Reply-To: <20140819162151.GA15166@forwiss.uni-passau.de>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On Tue, 19 Aug 2014 18:21:52 +0200
M G Berberich <btrfs@oss.m-berberich.de> wrote:
> · BtrFS with RAID1 is fairly stable.
Maybe, but it's not optimized for performance: reads are not balanced in the
most optimal way, and writes may end up being submitted sequentially rather
than in parallel to two devices, resulting in write performance that's way
less than that of a single device.
> · RAID 5/6 spreads all data over all devices, leading to performance
> problems on large diskarrays, and there is no option to limit the
> numbers of disk per stripe so far.
AFAIK Btrfs RAID 5/6 is not yet ready to be used in a production environment;
In your case I would recommend considering Btrfs on top of two 12-disk mdadm
RAID6 arrays, or three 8-disk ones, leaving one HDD as a shared hot spare.
To join the mdadm arrays into a larger block device you can use either LVM, or
Btrfs itself, with the "single" profile for data.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-08-19 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 16:21 Questions on using BtrFS for fileserver M G Berberich
2014-08-19 16:56 ` Kyle Manna
2014-08-19 19:05 ` Austin S Hemmelgarn
2014-08-19 21:09 ` Mitch Harder
2014-08-19 21:38 ` Andrej Manduch
2014-08-20 15:23 ` Austin S Hemmelgarn
2014-08-19 21:50 ` Roman Mamedov [this message]
2014-08-20 3:22 ` Marc MERLIN
2014-08-21 20:20 ` Andrew E. Mileski
-- strict thread matches above, loose matches on Subject: below --
2014-08-20 9:23 Tomasz Chmielewski
2014-08-20 13:41 ` Benjamin O'Connor
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=20140820035038.40d09071@natsu \
--to=rm@romanrm.net \
--cc=btrfs@oss.m-berberich.de \
--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).