From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
Subject: Re: btrfs on RHEL7 (kernel 3.10.0) production ready?
Date: Sat, 3 Aug 2019 12:01:12 -0600 [thread overview]
Message-ID: <CAJCQCtSm2a_UNYgue_Ha-JBCXpxrzZh2J5zHfkAXwHdRodJ8Fw@mail.gmail.com> (raw)
In-Reply-To: <20190803100928.GB29941@tik.uni-stuttgart.de>
On Sat, Aug 3, 2019 at 4:09 AM Ulli Horlacher
<framstag@rus.uni-stuttgart.de> wrote:
>
> I have RHEL 7 and CentOS 7.6 servers with kernel 3.10.0 and btrfs-progs v4.9.1
> Is btrfs there ready for production usage(*)?
No, Btrfs is deprecated in RHEL.
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.4_Release_Notes/chap-Red_Hat_Enterprise_Linux-7.4_Release_Notes-Deprecated_Functionality.html
Discussion here:
https://lwn.net/Articles/729488/
https://news.ycombinator.com/item?id=14907771
https://access.redhat.com/discussions/3138231
If you want to use Btrfs in production, and have distribution support,
you'd need to consider SUSE. If you want a similar feature set to
Btrfs, but remain supported on RHEL, you'd need to discuss it with
your Red Hat account manager.
If upstream support for Btrfs is adequate then you'll want to use a
recent stable kernel, and have a test and update strategy for
balancing out the risk of incorporating new kernels as they're
released vs the risk of using a fixed kernel version that grows stale
over time.
--
Chris Murphy
prev parent reply other threads:[~2019-08-03 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 10:09 btrfs on RHEL7 (kernel 3.10.0) production ready? Ulli Horlacher
2019-08-03 11:19 ` Nikolay Borisov
2019-08-03 12:24 ` Adam Borowski
2019-08-03 18:01 ` Chris Murphy [this message]
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=CAJCQCtSm2a_UNYgue_Ha-JBCXpxrzZh2J5zHfkAXwHdRodJ8Fw@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=framstag@rus.uni-stuttgart.de \
--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).