From: Roman Mamedov <rm@romanrm.net>
To: Imran Geriskovan <imran.geriskovan@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 4.10/4.11 Experiences
Date: Fri, 17 Feb 2017 13:43:37 +0500 [thread overview]
Message-ID: <20170217134337.6610299d@natsu> (raw)
In-Reply-To: <CAK5rZE4=34O2d+Tz8=r=_u2tMsipB3OKh3c3YWukX-YzL1JCaA@mail.gmail.com>
On Thu, 16 Feb 2017 13:37:53 +0200
Imran Geriskovan <imran.geriskovan@gmail.com> wrote:
> What are your experiences for btrfs regarding 4.10 and 4.11 kernels?
> I'm still on 4.8.x. I'd be happy to hear from anyone using 4.1x for
> a very typical single disk setup. Are they reasonably stable/good
> enough for this case?
You should always check with https://www.kernel.org/ what are the current
versions and what is their status. As you can see, 4.8 is basically dead in
the water, nowhere seen on the website, it does not get any updates anymore
by the kernel devs. If yours is a distro kernel, you now have to rely on
whatever fixes (and with what kind of quality) the distro maintainers are able
to backport.
Personally I took a liking to always running the latest longterm series, i.e.
right now staying on 4.4 and after a few initial hiccups it appears rock-solid
Btrfs-wise (as you said for single device, no multi-devices, no qgroup etc).
I'd suggest that you either upgrade to 4.9 (from the news it appears that one
will be granted the next longterm serues status), or switch to 4.4, which may
or may not be less preferable, given there are some scary sounding reports
about 4.9 (if you have this list's archive, search for "4.9" in thread
titles) with little to no conclusive resolutions.
--
With respect,
Roman
prev parent reply other threads:[~2017-02-17 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 11:32 4.10/4.11 Experiences Imran Geriskovan
2017-02-16 11:37 ` Imran Geriskovan
2017-02-16 14:07 ` 4.9/4.10 Experiences Adam Borowski
2017-02-17 8:43 ` Roman Mamedov [this message]
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=20170217134337.6610299d@natsu \
--to=rm@romanrm.net \
--cc=imran.geriskovan@gmail.com \
--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).