From: Chris Murphy <lists@colorremedies.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: Brendan Hide <brendan@swiftspirit.co.za>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs
Date: Fri, 3 Jun 2016 20:36:15 -0600 [thread overview]
Message-ID: <CAJCQCtRi8C-Grcff4MaS9-amoSuAwcdMFzUooA0PQSFQQTBpMQ@mail.gmail.com> (raw)
In-Reply-To: <1465006419.6648.54.camel@scientia.net>
On Fri, Jun 3, 2016 at 8:13 PM, Christoph Anton Mitterer
<calestyo@scientia.net> wrote:
> If there would be e.g. an kept-up-to-date wiki page about the status
> and current perils of e.g. RAID5/6, people (like me) wouldn't ask every
> weeks, saving the devs' time.
Well up until 4.6, there was a rather clear "Btrfs is under heavy
development, and is not suitable for-any uses other than benchmarking
and review." statement in kernel documentation.
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/diff/Documentation/filesystems/btrfs.txt?id=v4.6&id2=v4.5
There's no longer such a strongly worded caution in that document, nor
in the wiki.
The wiki has stale information still, but it's a volunteer effort like
everything else Btrfs related.
--
Chris Murphy
next prev parent reply other threads:[~2016-06-04 2:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 22:25 raid5/6 production use status? Christoph Anton Mitterer
2016-06-02 9:24 ` Gerald Hopf
2016-06-02 9:35 ` Hugo Mills
2016-06-02 10:03 ` Gerald Hopf
2016-06-03 17:38 ` btrfs (was: raid5/6) production use status (and future)? Christoph Anton Mitterer
2016-06-03 19:50 ` btrfs Austin S Hemmelgarn
2016-06-04 1:51 ` btrfs Christoph Anton Mitterer
2016-06-04 7:24 ` btrfs Andrei Borzenkov
2016-06-04 17:00 ` btrfs Chris Murphy
2016-06-04 17:37 ` btrfs Christoph Anton Mitterer
2016-06-04 19:13 ` btrfs Chris Murphy
2016-06-04 22:43 ` btrfs Christoph Anton Mitterer
2016-06-05 15:51 ` btrfs Chris Murphy
2016-06-05 20:39 ` btrfs Christoph Anton Mitterer
2016-06-04 21:18 ` btrfs Andrei Borzenkov
2016-06-05 20:39 ` btrfs Henk Slager
2016-06-05 20:56 ` btrfs Christoph Anton Mitterer
2016-06-05 21:07 ` btrfs Hugo Mills
2016-06-05 21:31 ` btrfs Christoph Anton Mitterer
2016-06-05 23:39 ` btrfs Chris Murphy
2016-06-08 6:13 ` btrfs Duncan
2016-06-06 0:56 ` btrfs Chris Murphy
2016-06-06 13:04 ` btrfs Austin S. Hemmelgarn
[not found] ` <f4a9ef2f-99a8-bcc4-5a8f-b022914980f0@swiftspirit.co.za>
2016-06-04 2:13 ` btrfs Christoph Anton Mitterer
2016-06-04 2:36 ` Chris Murphy [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-15 15:32 btrfs Turritopsis Dohrnii Teo En Ming
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=CAJCQCtRi8C-Grcff4MaS9-amoSuAwcdMFzUooA0PQSFQQTBpMQ@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=brendan@swiftspirit.co.za \
--cc=calestyo@scientia.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 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).