From: Eric Sandeen <sandeen@redhat.com>
To: Chris Murphy <lists@colorremedies.com>,
Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Austin S Hemmelgarn <ahferroin7@gmail.com>,
Duncan <1i5t5.duncan@cox.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs and integration with GNU ++
Date: Tue, 19 May 2015 14:41:04 -0500 [thread overview]
Message-ID: <555B91D0.2060609@redhat.com> (raw)
In-Reply-To: <CAJCQCtRdQMt9w0svBGnWU0t8AbWEJ=s7i_z7namCXK_u5A4Brw@mail.gmail.com>
On 5/19/15 1:09 PM, Chris Murphy wrote:
> On Tue, May 19, 2015 at 11:09 AM, Roy Sigurd Karlsbakk
> <roy@karlsbakk.net> wrote:
>>>> Interesting - which ones is it that's doing this?
>>>>
>>> While I don't know of any that use it by _default_ yet, I do know that
>>> it is an easy to use option on most of the big non-comercial distros
>>> already (Debian, Fedora, Ubuntu, etc.), and a couple (Gentoo, Arch, and
>>> possibly Slackware) have had the option to use it since it went mainline
>>> (although that is just a side effect of the installation procedures, not
>>> any kind of active attempt at support).
>>
>> Seems CentOS 7 also allows for btrfs installs. Wonder if RHEL7 also would do that. Gotta test one day...
>
> Also, those CentOS/RHEL 7 kernels are old by Btrfs standards. You
> should consider using elrepo kernels (they have kernel 4.0.3 and 4.0.4
> right now), and if you can't do that, then I wouldn't use Btrfs, use
> XFS instead with those 3.10.x kernels.
FWIW, I have been keeping the btrfs codebase in RHEL7 as up to date as possible,
given release frequency constraints.
The kernel is based on 3.10, but the btrfs code is much newer.
-Eric
next prev parent reply other threads:[~2015-05-19 19:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 19:33 Btrfs and integration with GNU ++ Roy Sigurd Karlsbakk
2015-05-18 1:32 ` Qu Wenruo
2015-05-18 6:41 ` Duncan
2015-05-18 8:57 ` Duncan
2015-05-18 9:22 ` Roy Sigurd Karlsbakk
2015-05-18 11:58 ` Austin S Hemmelgarn
2015-05-18 14:31 ` Chris Murphy
2015-05-19 17:09 ` Roy Sigurd Karlsbakk
2015-05-19 18:05 ` Chris Murphy
2015-05-19 18:09 ` Chris Murphy
2015-05-19 19:41 ` Eric Sandeen [this message]
2015-05-19 20:04 ` Chris Murphy
2015-05-20 6:45 ` Duncan
2015-05-18 14:24 ` Chris Murphy
2015-05-19 7:24 ` Russell Coker
2015-05-19 11:56 ` Austin S Hemmelgarn
2015-05-19 18:02 ` Chris Murphy
2015-05-20 18:04 ` Zygo Blaxell
2015-05-20 18:02 ` David Sterba
2015-05-18 15:14 ` Eric Sandeen
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=555B91D0.2060609@redhat.com \
--to=sandeen@redhat.com \
--cc=1i5t5.duncan@cox.net \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=roy@karlsbakk.net \
/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;
as well as URLs for NNTP newsgroup(s).