linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: Shriramana Sharma <samjnaa@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Distro vs latest kernel for BTRFS?
Date: Fri, 22 Aug 2014 19:38:59 +0200	[thread overview]
Message-ID: <5464164.8Uxj5nlT6d@merkaba> (raw)
In-Reply-To: <CAH-HCWVMO+NO0B5i0o0gCHBy9dLjc08gcqxT7oEV5WkO2BHvMA@mail.gmail.com>

Am Freitag, 22. August 2014, 17:29:29 schrieb Shriramana Sharma:
> Hello. I've seen repeated advices to use the latest kernel. While
> hearing of the recent compression bug affecting recent kernels does
> somewhat warn one off the previous advice, I would like to know what
> people who are running regular distros do to get the latest kernel.
> 
> Personally I'm on Kubuntu, which provides mainline kernels till a
> particular point but not beyond that.
> 
> Do people here always compile the latest kernel themselves just to get
> the latest BTRFS stability fixes (and  improvements, though as a
> second priority)?

I compile own kernel on my main laptop cause I want to follow kernel 
development closely for my Linux Performance analysis and tuning trainings and 
also help a bit with testing things.

I don´t compile kernels on any other machines anymore. Instead I use what 
Debian Sid gives me. On the server VM I use 3.14 Debian Wheezy Backports 
kernel, an will continue to do so, until I know a 3.16 package with BTRFS fixes 
hits the backports repo.

I recommend against SLES 11 SP 3 stable kernel. Their 3.0 had serious free 
space issues in one VM after *just* installing OpenLDAP and have snapper 
continue with the snapshotting. It was still 2GB free, but I was not able to 
delete files or delete snapshots anymore. I think I also try rebalancing the 
FS. After a while I gave up and reverted to a previous VM snapshot.

I know this is supported officially, but I don´t think this is anywhere near 
production ready. SLES 12 should be much better as its using a newer kernel.

On any account long time enterprise Linux kernels may easily become outdated. 
I know they are backporting things, but I think for BTRFS its better to follow 
new kernels as is more timely.

With the distros that release all 6 months or so, I think you get recent 
enough kernel easily. With Debian you can use backport kernels. Some distros 
have additionally kernel repos for more recent kernels. And I in the end I 
think you can even install newer kernel packages on enterprise distros, but… 
you loose support this way.

For Kubuntu / Ubuntu I think there even is a daily kernel PPA. I think 
Phoronix uses it for their daily performance regression testing (and making 
big noise of regressions even in RC kernels).

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  parent reply	other threads:[~2014-08-22 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 11:59 Distro vs latest kernel for BTRFS? Shriramana Sharma
2014-08-22 12:04 ` Austin S Hemmelgarn
2014-08-22 18:09   ` Duncan
2014-08-22 18:22   ` Rich Freeman
2014-08-22 19:18     ` Austin S Hemmelgarn
2014-08-22 14:10 ` Marc MERLIN
2014-08-22 16:51 ` Chris Murphy
2014-08-22 17:38 ` Martin Steigerwald [this message]
2014-08-25  1:06 ` Qu Wenruo

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=5464164.8Uxj5nlT6d@merkaba \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=samjnaa@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).