From: Adam Borowski <kilobyte@angband.pl>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs on RHEL7 (kernel 3.10.0) production ready?
Date: Sat, 3 Aug 2019 14:24:23 +0200 [thread overview]
Message-ID: <20190803122423.GA6703@angband.pl> (raw)
In-Reply-To: <20190803100928.GB29941@tik.uni-stuttgart.de>
On Sat, Aug 03, 2019 at 12:09:28PM +0200, Ulli Horlacher 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(*)?
Hell no!
It's a truly ancient kernel, from the times btrfs wasn't considered stable.
There's a lot of backports atop it, which for a quickly evolving filesystem
are pretty unsafe unless there's a large team doing that work.
And unlike SLES, there's none. This led to notorious breakages, with Red
Hat finally declaring btrfs unsupported on their distributions.
Thus, if you care about your data at all, please use a modern kernel.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out,
⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the
⠈⠳⣄⠀⠀⠀⠀ sky. Your cat demands food. The priority should be obvious...
next prev parent reply other threads:[~2019-08-03 12:25 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 [this message]
2019-08-03 18:01 ` Chris Murphy
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=20190803122423.GA6703@angband.pl \
--to=kilobyte@angband.pl \
--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).