From: M G Berberich <btrfs@oss.m-berberich.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Questions on using BtrFS for fileserver
Date: Tue, 19 Aug 2014 18:21:52 +0200 [thread overview]
Message-ID: <20140819162151.GA15166@forwiss.uni-passau.de> (raw)
Hello,
we are thinking about using BtrFS on standard hardware for a
fileserver with about 50T (100T raw) of storage (25×4TByte).
This is what I understood so far. Is this right?
· incremental send/receive works.
· There is no support for hotspares (spare disks that automatically
replaces faulty disk).
· BtrFS with RAID1 is fairly stable.
· 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.
Some questions:
· There where reports, that bcache with btrfs leads to corruption. Is
this still so?
· If a disk failes, does BtrFS rebalance automatically? (This would
give a a kind o hotspare behavior)
· Besides using bcache, are there any possibilities to boost
performance by adding (dedicated) cache-SSDs to a BtrFS?
· Are there any reports/papers/web-pages about BtrFS-systems this size
in use? Praises, complains, performance-reviews, whatever…
MfG
bmg
--
„Des is völlig wurscht, was heut beschlos- | M G Berberich
sen wird: I bin sowieso dagegn!“ | berberic@fmi.uni-passau.de
(SPD-Stadtrat Kurt Schindler; Regensburg) | www.fmi.uni-passau.de/~berberic
next reply other threads:[~2014-08-19 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 16:21 M G Berberich [this message]
2014-08-19 16:56 ` Questions on using BtrFS for fileserver 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
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=20140819162151.GA15166@forwiss.uni-passau.de \
--to=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).