From: Lists <lists@benjamindsmith.com>
To: linux-btrfs@vger.kernel.org
Subject: Testing BTRFS
Date: Mon, 10 Mar 2014 17:39:32 -0700 [thread overview]
Message-ID: <531E5B44.6030502@benjamindsmith.com> (raw)
In-Reply-To: <pan$72cea$1961f20d$d4386bc$889c1510@cox.net>
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?
-Ben
next prev parent reply other threads:[~2014-03-11 0:48 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 ` Lists [this message]
2014-03-11 1:02 ` Testing BTRFS 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
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=531E5B44.6030502@benjamindsmith.com \
--to=lists@benjamindsmith.com \
--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