From: Marc MERLIN <marc@merlins.org>
To: M G Berberich <btrfs@oss.m-berberich.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Questions on using BtrFS for fileserver
Date: Tue, 19 Aug 2014 20:22:05 -0700 [thread overview]
Message-ID: <20140820032205.GL3875@merlins.org> (raw)
In-Reply-To: <20140819162151.GA15166@forwiss.uni-passau.de>
On Tue, Aug 19, 2014 at 06:21:52PM +0200, M G Berberich wrote:
> · incremental send/receive works.
Yes.
> · There is no support for hotspares (spare disks that automatically
> replaces faulty disk).
Correct
> · BtrFS with RAID1 is fairly stable.
>From what I know.
> · 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.
Not sure about the performance issue, but either way, don't use RAID5/6
with btrfs for anything else than playing around. The code is not
finished.
> · If a disk failes, does BtrFS rebalance automatically? (This would
> give a a kind o hotspare behavior)
No, not for raid5/6.
> · Are there any reports/papers/web-pages about BtrFS-systems this size
> in use? Praises, complains, performance-reviews, whatever…
Use md-raid5 which is known and true, and put btrfs on top.
And still have backups, be ready for btrfs to become unusable (speed
and/or deadlocks), get trashed, or some other problem.
It's not guaranteed to happen, but the odds are far from being 0 either,
so either your data is throwaway, or have good backups.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-08-20 4:06 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
2014-08-20 3:22 ` Marc MERLIN [this message]
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=20140820032205.GL3875@merlins.org \
--to=marc@merlins.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.