From: Chris Mason <clm@fb.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: RAID56 status?
Date: Mon, 23 Jan 2017 18:18:09 -0500 [thread overview]
Message-ID: <20170123231809.GA9114@clm-mbp.masoncoding.com> (raw)
In-Reply-To: <1485194001.21584.1.camel@scientia.net>
On Mon, Jan 23, 2017 at 06:53:21PM +0100, Christoph Anton Mitterer wrote:
>Just wondered... is there any larger known RAID56 deployment? I mean
>something with real-world production systems and ideally many different
> IO scenarios, failures, pulling disks randomly and perhaps even so
>many disks that it's also likely to hit something like silent data
>corruption (on the disk level)?
>
>Has CM already migrated all of Facebook's storage to btrfs RAID56?! ;-)
>Well at least facebook.com seems till online ;-P *kidding*
>
>I mean the good thing in having such a massive production-like
>environment - especially when it's not just one homogeneous usage
>pattern - is that it would help to build up quite some trust into the
>code (once the already known bugs are fixed).
We've been focusing on the single-drive use cases internally. This year
that's changing as we ramp up more users in different places.
Performance/stability work and raid5/6 are the top of my list right now.
-chris
next prev parent reply other threads:[~2017-01-23 23:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 21:22 RAID56 status? Jan Vales
2017-01-22 22:35 ` Christoph Anton Mitterer
2017-01-22 22:39 ` Hugo Mills
2017-01-22 22:48 ` Waxhead
2017-01-22 22:56 ` Christoph Anton Mitterer
2017-01-23 0:25 ` Jan Vales
2017-01-23 1:34 ` Qu Wenruo
[not found] ` <CALqCWCXNoKqAJR=7c4wzOvVjSBxNRMsUYMvkfRMcVk14dkp27Q@mail.gmail.com>
2017-01-23 5:24 ` Qu Wenruo
2017-01-23 17:53 ` Christoph Anton Mitterer
2017-01-23 23:18 ` Chris Mason [this message]
2017-01-23 23:31 ` Christoph Anton Mitterer
2017-01-24 14:36 ` Niccolò Belli
2017-01-23 6:57 ` Brendan Hide
2017-01-23 8:34 ` Janos Toth F.
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=20170123231809.GA9114@clm-mbp.masoncoding.com \
--to=clm@fb.com \
--cc=calestyo@scientia.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 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.