From: Julian Taylor <jtaylor.debian@googlemail.com>
To: Martin <rc6encrypted@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Recommended why to use btrfs for production?
Date: Fri, 3 Jun 2016 15:47:31 +0200 [thread overview]
Message-ID: <57518A73.5030201@googlemail.com> (raw)
In-Reply-To: <CAGQ70YeZzDgiT_v1Z0eGcWsn8prnji30hCkyjrBg8vNziLUkiQ@mail.gmail.com>
On 06/03/2016 03:31 PM, Martin wrote:
>> In general, avoid Ubuntu LTS versions when dealing with BTRFS, as well as
>> most enterprise distros, they all tend to back-port patches instead of using
>> newer kernels, which means it's functionally impossible to provide good
>> support for them here (because we can't know for sure what exactly they've
>> back-ported). I'd suggest building your own kernel if possible, with Arch
>> Linux being a close second (they follow upstream very closely), followed by
>> Fedora and non-LTS Ubuntu.
>
> Then I would build my own, if that is the preferred option.
>
Ubuntu also provides newer kernels for their LTS via the Hardware
Enablement Stack:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
So if you can live with about 6 month time lag and shorter support for
the non-lts versions of those kernels that is a good option.
As you can see 16.04 currently provides 4.4 and the next update will
likely be 4.8.
next prev parent reply other threads:[~2016-06-03 13:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 9:49 Recommended why to use btrfs for production? Martin
2016-06-03 9:53 ` Marc Haber
2016-06-03 9:57 ` Martin
2016-06-03 10:01 ` Hans van Kranenburg
2016-06-03 10:15 ` Martin
2016-06-03 12:55 ` Austin S. Hemmelgarn
2016-06-03 13:31 ` Martin
2016-06-03 13:47 ` Julian Taylor [this message]
2016-06-03 14:21 ` Austin S. Hemmelgarn
2016-06-03 14:39 ` Martin
2016-06-03 19:09 ` Christoph Anton Mitterer
2016-06-09 6:16 ` Duncan
2016-06-09 11:38 ` Austin S. Hemmelgarn
2016-06-09 17:39 ` Chris Murphy
2016-06-09 19:57 ` Duncan
2016-06-03 14:05 ` Chris Murphy
2016-06-03 14:11 ` Martin
2016-06-03 15:33 ` Austin S. Hemmelgarn
2016-06-04 0:48 ` Nicholas D Steeves
2016-06-04 1:48 ` Chris Murphy
2016-06-06 13:29 ` Austin S. Hemmelgarn
2016-06-04 1:34 ` Chris Murphy
2016-06-05 10:45 ` Mladen Milinkovic
2016-06-05 16:33 ` James Johnston
2016-06-05 18:20 ` Andrei Borzenkov
2016-06-06 1:47 ` Chris Murphy
2016-06-06 2:40 ` James Johnston
2016-06-06 13:36 ` Austin S. Hemmelgarn
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=57518A73.5030201@googlemail.com \
--to=jtaylor.debian@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rc6encrypted@gmail.com \
/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).