From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: btrfs on RHEL7 (kernel 3.10.0) production ready?
Date: Sat, 3 Aug 2019 12:09:28 +0200 [thread overview]
Message-ID: <20190803100928.GB29941@tik.uni-stuttgart.de> (raw)
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(*)?
I will not use any btrfs RAID modes, because I have hardware RAID.
I just want to use (some few) snapshots.
The filesystem will have 50 TB and the server (VM) has 8 CPUs and 8 GB RAM.
Any recommendations?
(*) A (web based) file server, see https://fex.rus.uni-stuttgart.de/
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<20190803100928.GB29941@tik.uni-stuttgart.de>
next reply other threads:[~2019-08-03 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 10:09 Ulli Horlacher [this message]
2019-08-03 11:19 ` btrfs on RHEL7 (kernel 3.10.0) production ready? Nikolay Borisov
2019-08-03 12:24 ` Adam Borowski
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=20190803100928.GB29941@tik.uni-stuttgart.de \
--to=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).