public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Avi Miller <avi.miller@oracle.com>, Lists <lists@benjamindsmith.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Testing BTRFS
Date: Tue, 11 Mar 2014 14:08:02 -0500	[thread overview]
Message-ID: <531F5F12.4080009@redhat.com> (raw)
In-Reply-To: <DFAE9B5E-2C12-4215-B4CA-016CBD4575EC@oracle.com>

On 3/10/14, 8:02 PM, Avi Miller wrote:
> 
> On 11 Mar 2014, at 11:39 am, Lists <lists@benjamindsmith.com> wrote:
> 
>> Is there a "recommended way" to do this? Is it anywhere as easy as
>> ZFSonLinux yum install?
> 
> Oracle Linux 6 with the Unbreakable Enterprise Kernel Release 2 or
> Release 3 has production-ready btrfs support. You can even convert
> your existing CentOS6 boxes across to Oracle Linux 6 in-place without
> reinstalling:
> 
> http://linux.oracle.com/switch/centos/

If we're plugging distros... I can also tell you that you can install
upcoming RHEL7 on btrfs if you like, and it has a very up-to-date
btrfs codebase.  Of course Fedora and other "non-enterprise" distros
have btrfs support as well.

But we're keeping it "tech preview" in RHEL7 for now, because in our
testing, it does not yet reach the level of reliability that we
wish to provide to our customers.

Indeed, testing 3.8.13-26.2.1.el6uek.x86_64 (which is, I believe,
the kernel which Avi referred to) via xfstests, I saw
failures on btrfs/009 and btrfs/022; then the box deadlocked
on btrfs/024.  I rebooted & resumed, then deadlocked on btrfs/030.
Rebooted and resumed again, then panicked on btrfs/035.  At that
point I stopped.

Ben, the best advice I have for you is to test *your* workload
on btrfs with whatever qualification tests you have, and see how
things fare.  If you want to know the current state of btrfs,
test the upstream code as best you can; if you hope to deploy
on a distribution with a longer support window, test on that
distribution.

But I agree with Josef that for now, the fixes and changes are
still flying fast & furious, and except in limited use cases,
btrfs is not yet ready for general commercial deployment.

-Eric

  reply	other threads:[~2014-03-11 19:08 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 [this message]
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=531F5F12.4080009@redhat.com \
    --to=sandeen@redhat.com \
    --cc=avi.miller@oracle.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