From: Bostjan Skufca <bostjan@a2o.si>
To: Hugo Mills <hugo@carfax.org.uk>, Sjoerd <sjoerd@sjomar.eu>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Latest kernel to use?
Date: Fri, 25 Sep 2015 16:34:16 +0200 [thread overview]
Message-ID: <CAEp_DRCiMRzuX8m9JoNO=8rtSWSP_Vqs4LfVW7JppDa2c4e_7w@mail.gmail.com> (raw)
In-Reply-To: <20150925135134.GF3749@carfax.org.uk>
On 25 September 2015 at 15:51, Hugo Mills <hugo@carfax.org.uk> wrote:
> On Fri, Sep 25, 2015 at 03:36:18PM +0200, Sjoerd wrote:
>> Thanks all for the feedback. Still doubting though to go for 4.2.1 or not.
>> Main reason is that I am currently running 4.1.7 on my laptop which seems to
>> work fine and had some issues with the 4.2.0 kernel. No issues I thing that
>> were btrfs related, but more related to my nvidia card. Anyway switching back
>> to 4.1.7 resolved those, so I am a bit holding back to try the 4.2.1 version
>> ;)
>> Anyway I'll see and can always revert back if I don't like it ;)
>
> If 4.1.7 is working OK for you, stick with it. It's getting much
> less important now, as btrfs matures, to keep up with the _very_
> latest. Purely on gut feeling about issues we see on IRC and here,
> 3.19 or later would be reasonable at the moment.
Similar here: I am sticking with 3.19.2 which has proven to work fine
for me (backup systems with btrfs on lvm, lots of snapshots/subvolumes
and occasional rebalance, no fancy/fresh stuff like btrfs-raid, online
compression or subvolume quota, though this last one is tempting in my
use case).
b.
next prev parent reply other threads:[~2015-09-25 14:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 21:07 Latest kernel to use? Sjoerd
2015-09-24 21:18 ` Hugo Mills
2015-09-25 11:20 ` Austin S Hemmelgarn
2015-09-25 13:12 ` Rich Freeman
2015-09-25 13:43 ` Roman Mamedov
[not found] ` <CAEp_DRB7zaHmJnghJzVR++_OO+4mrM_+jCjrYAQJcNUXpM=bAQ@mail.gmail.com>
2015-09-25 17:00 ` Rich Freeman
2015-09-25 17:41 ` Bostjan Skufca
2015-09-25 13:36 ` Sjoerd
2015-09-25 13:51 ` Hugo Mills
2015-09-25 14:34 ` Bostjan Skufca [this message]
2015-09-26 2:04 ` Duncan
2015-09-25 14:35 ` Sjoerd
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='CAEp_DRCiMRzuX8m9JoNO=8rtSWSP_Vqs4LfVW7JppDa2c4e_7w@mail.gmail.com' \
--to=bostjan@a2o.si \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=sjoerd@sjomar.eu \
/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).