From: Josef Bacik <jbacik@fb.com>
To: Lists <lists@benjamindsmith.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Testing BTRFS
Date: Tue, 11 Mar 2014 09:33:43 -0400 [thread overview]
Message-ID: <531F10B7.8010309@fb.com> (raw)
In-Reply-To: <531E5B44.6030502@benjamindsmith.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/10/2014 08:39 PM, Lists wrote:
> I'd like to begin testing BTRFS. We'd probably begin roll out in 6
> months to a year if testing goes well.
>
> We're currently using CentOS6/64 everywhere, are aware of BTRFS
> being a "Technology preview" in RHEL 7beta and would like to begin
> testing production-level load testing. We generate about 10 GB of
> distinct data daily that is stored redundantly by default on a
> combination of ZFS and Ext4.
>
> Is there a "recommended way" to do this? Is it anywhere as easy as
> ZFSonLinux yum install?
>
>
There is way too much churn for any "enterprise" distro to be able to
keep up with bugfixes and stuff. You are best off rolling your own
kernel based on the stable series if you want to think about using
btrfs in production. Thanks,
Josef
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTHxCtAAoJEANb+wAKly3BdJ8QAK5hYoNtJT/UEkpKakpNoXfV
q6lg2NVPT6EeHzcMhTRS+VTOJ/bjvfwX0qDxRkjvo73F+nkQYcrO78cEMvPqtwTq
HKxrGMibCtt5PlzzcbKqSc1VGIDFEkD2z7fr5y2n4V+E5x0EPCFxU6VOjXgqXyEZ
8tKW24oxLAwbWBvyiaKrB/gWm47Aw6p2pVWgWrqMjMFUaNQBoisAU+1Ezn0Xjg6w
4wazfGqUkUZ3pMcZr5IMQ9X+p+FUid7JWcdNwPjIsPMQhP7mkIK0Mq8eDu6ijVv2
nI52pZuYaZs3+7OlkEoHRssnAwIWUwUq9UQwRjl4WK8FrpgdyYe0n2zlZIWGinvF
qZRMmB5PtM+SYT9Wt5OPAgZxb/ivc9Vz7ACG4edNSBqZ1D7+52aazT4JY0fqWGGU
8vapdKUmyXPQT9MphvHUEqnJtA/K9ek8Frt+f304KCcl/0IEESAoo3InlS7Hw45D
ANEO4ZCwaUp/WjhqvwuvhYrqn8ENsbCm31RYAvAGEOoROzwXEnbl/Nv4DaKa+Q7b
I6uSpyS60cNA2wmKm3wzFGpvSkP8PMzA1zSepK/yJ9p3PxUdxUpY1OqYc8y7gqOf
+ACNUuNMbNwAhMb9udEZzuBZojX3/vVPlqOWLPYDr3fVCrDIwuSKtloao+czkrpo
sxJbe80q3rqtw+p0pStO
=n1mD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-03-11 13:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 18:18 Understanding btrfs and backups Eric Mesa
2014-03-06 21:33 ` Duncan
2014-03-07 10:13 ` Wolfgang Mader
2014-03-09 15:46 ` Duncan
2014-03-07 14:03 ` Eric Mesa
2014-03-07 15:14 ` Sander
2014-03-09 4:13 ` Chris Samuel
2014-03-09 15:30 ` Duncan
2014-03-13 8:18 ` Chris Samuel
2014-03-09 16:40 ` Duncan
2014-03-11 0:39 ` Testing BTRFS Lists
2014-03-11 1:02 ` Avi Miller
2014-03-11 19:08 ` Eric Sandeen
2014-03-11 20:30 ` Avi Miller
2014-03-12 11:15 ` xfstests btrfs/035 (was Re: Testing BTRFS) David Disseldorp
2014-03-13 18:10 ` Testing BTRFS Lists
2014-03-13 20:20 ` Avi Miller
2014-03-11 13:33 ` Josef Bacik [this message]
2014-03-13 17:12 ` Understanding btrfs and backups Chris Murphy
2014-03-17 5:42 ` Understanding btrfs and backups => automatic snapshot script Marc MERLIN
2014-03-21 5:57 ` Marc MERLIN
2014-03-21 7:41 ` Duncan
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=531F10B7.8010309@fb.com \
--to=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@benjamindsmith.com \
/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