linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs and integration with GNU ++
Date: Tue, 19 May 2015 14:04:56 -0600	[thread overview]
Message-ID: <CAJCQCtSENLFXdBAxTRe74prRpqyHi5wCoy4--Y-Zr4SFA_YHBw@mail.gmail.com> (raw)
In-Reply-To: <555B91D0.2060609@redhat.com>

On Tue, May 19, 2015 at 1:41 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> On 5/19/15 1:09 PM, Chris Murphy wrote:
>> 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.

That's good to know. Thanks for that!

-- 
Chris Murphy

  reply	other threads:[~2015-05-19 20:04 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
2015-05-19 20:04             ` Chris Murphy [this message]
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=CAJCQCtSENLFXdBAxTRe74prRpqyHi5wCoy4--Y-Zr4SFA_YHBw@mail.gmail.com \
    --to=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).