From: Lists <lists@benjamindsmith.com>
To: Avi Miller <avi.miller@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Testing BTRFS
Date: Thu, 13 Mar 2014 11:10:47 -0700 [thread overview]
Message-ID: <5321F4A7.8080003@benjamindsmith.com> (raw)
In-Reply-To: <DFAE9B5E-2C12-4215-B4CA-016CBD4575EC@oracle.com>
On 03/10/2014 06:02 PM, Avi Miller wrote:
> 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/
>
> Oracle also now provides all errata, including security and bug fixes for free athttp://public-yum.oracle.com and our kernel source code can be found athttps://oss.oracle.com/git/
Is there any issue with BTRFS and 32 bit O/S like with ZFS?
-Ben
next prev parent reply other threads:[~2014-03-13 18:10 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 ` Lists [this message]
2014-03-13 20:20 ` Testing BTRFS 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=5321F4A7.8080003@benjamindsmith.com \
--to=lists@benjamindsmith.com \
--cc=avi.miller@oracle.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 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.