From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
Date: Tue, 29 Dec 2015 16:44:12 +0000 (UTC) [thread overview]
Message-ID: <pan$77b8$70538e05$c21bb62d$4aa6e02@cox.net> (raw)
In-Reply-To: 1451403179.13713.11.camel@scientia.net
Christoph Anton Mitterer posted on Tue, 29 Dec 2015 16:32:59 +0100 as
excerpted:
>> From Documentation/filesystems/BTRFS.txt:
>> Btrfs is under heavy development, and is not suitable for any uses
>> other than benchmarking and review.
> Well I guess now it's time for Duncan's usual "stable or not" talk
> (@Duncan, I think by now, you should have made it into some verse or
> ballad form... :D for general pleasure ;) )
=:^)
The devs did remove most of the experimental warnings some versions ago.
I guess they missed that one. The "heavy development" part is definitely
still correct, but with the caveats below, I don't believe the "only
benchmarking and review" fits the generally held list position, these
days.
As I normally put it, btrfs is "definitely stabilizING, but not yet
entirely stable and mature." What that means in real life is that while
not yet recommended for production use where down time costs money and
potentially jobs, it's generally ready for routine daily use, PROVIDED
one observes the usual admin's rule of backups, that for any level of
backup, either you have it, or you consider the data it would cover to be
worth less than the hassle and resources that backup would take, modified
by the risk factor of actually having to use the backup. Because btrfs
is still stabilizing, that risk factor remains somewhat elevated, so you
better have at least 1-2 levels of backup if you don't consider the data
of trivial throw-away value.
Beyond that, keeping up with the list and staying relatively current with
your kernel and btrfs-progs userspace are strongly recommended as well.
But it's definitely not recommended yet for the conservative stability
types that run half a decade old "stable" enterprise distros. That sort
of use-case is in basic conflict with where btrfs is at this point, and
people wishing to run it should be looking to some other filesystem, or
if they /do/ choose to take up the enterprise distros on their offer of
support for btrfs, should be looking to them for that support, as it's
them that are choosing to offer it, while the general position on the
list seems to be "that's insane".
Similarly of course for those unwilling to do backups or run relatively
current kernels and btrfs userspace, or to keep up with the list. In
that case, btrfs isn't an appropriate choice for them.
But while not entirely stable and mature yet, that's still rather beyond
"not suitable for any uses other than benchmarking and review", and
indeed, most of the other wording of that nature was stripped around
kernel 3.12, and while some of us considered that a bit early, I think
most would agree that the "benchmarking and review" only wording is
somewhat dated, by now.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-12-29 16:44 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 12:24 [PATCH] BTRFS: Adds an option to select RAID Stripe size Sanidhya Solanki
2015-12-28 22:19 ` Christoph Anton Mitterer
2015-12-28 20:38 ` Sanidhya Solanki
2015-12-29 1:21 ` Christoph Anton Mitterer
2015-12-28 21:43 ` Sanidhya Solanki
2015-12-29 3:42 ` Christoph Anton Mitterer
2015-12-29 0:03 ` Sanidhya Solanki
2015-12-29 4:26 ` Christoph Anton Mitterer
2015-12-29 1:31 ` Sanidhya Solanki
2015-12-29 6:03 ` Christoph Anton Mitterer
2015-12-29 2:23 ` Sanidhya Solanki
2015-12-29 15:32 ` Christoph Anton Mitterer
2015-12-29 16:44 ` Duncan [this message]
2015-12-30 2:56 ` Christoph Anton Mitterer
2015-12-29 18:06 ` David Sterba
2015-12-30 20:00 ` Christoph Anton Mitterer
2015-12-30 21:02 ` Duncan
2015-12-30 21:13 ` Christoph Anton Mitterer
2016-01-02 11:52 ` Sanidhya Solanki
2016-01-03 1:37 ` Qu Wenruo
2016-01-03 2:26 ` Christoph Anton Mitterer
2016-01-05 10:44 ` David Sterba
2016-01-05 18:48 ` Christoph Anton Mitterer
2016-01-10 3:11 ` Sanidhya Solanki
2016-01-11 1:29 ` Qu Wenruo
2016-01-11 15:43 ` Christoph Anton Mitterer
2016-01-11 11:49 ` Sanidhya Solanki
2016-01-11 15:57 ` Christoph Anton Mitterer
2016-01-11 16:01 ` Hugo Mills
2016-01-12 12:23 ` Austin S. Hemmelgarn
2016-01-12 12:07 ` Sanidhya Solanki
2015-12-29 13:39 ` David Sterba
2015-12-29 11:15 ` Sanidhya Solanki
2015-12-29 17:06 ` David Sterba
2015-12-29 21:32 ` Sanidhya Solanki
2015-12-30 6:39 ` Sanidhya Solanki
2015-12-30 11:59 ` Qu Wenruo
2015-12-30 9:54 ` Sanidhya Solanki
2015-12-30 14:10 ` Qu Wenruo
2015-12-30 11:15 ` Sanidhya Solanki
2015-12-30 15:58 ` David Sterba
2015-12-30 21:19 ` Sanidhya Solanki
2015-12-30 16:17 ` David Sterba
2015-12-30 21:21 ` Sanidhya Solanki
2016-01-05 10:33 ` David Sterba
2015-12-31 0:46 ` Qu Wenruo
2016-01-05 10:16 ` David Sterba
2015-12-30 19:48 ` Christoph Anton Mitterer
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='pan$77b8$70538e05$c21bb62d$4aa6e02@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.