From: Roman Mamedov <rm@romanrm.net>
To: Rich Freeman <r-btrfs@thefreemanclan.net>
Cc: Austin S Hemmelgarn <ahferroin7@gmail.com>,
Sjoerd <sjoerd@sjomar.eu>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Latest kernel to use?
Date: Fri, 25 Sep 2015 18:43:00 +0500 [thread overview]
Message-ID: <20150925184300.1d67254b@natsu> (raw)
In-Reply-To: <CAGfcS_nFn=AH6Y-4dFQEmy42KVJLBvLuaEHRtoYrBDUtNategw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
On Fri, 25 Sep 2015 09:12:15 -0400
Rich Freeman <r-btrfs@thefreemanclan.net> wrote:
> I'll just say that my btrfs stability has gone WAY up when I stopped
> following this advice and instead followed a recent longterm. Right
> now I'm following 3.18. There were some really bad corruption issues
> in 3.17/18/19 that burned me, and today while considering moving up to
> 4.1 I'm still seeing a lot of threads about issues during balance/etc.
> I still run into the odd issue with 3.18, but not nearly to the degree
> that I used to.
>
> Now, I would stick with a recent longterm. The older longterms go
> back to a time when btrfs was far more experimental. Even 3.16
> probably has a lot of issues that are fixed in 3.18.
Absolutely that! I was pondering whether or not to chime in with my praise of
"longterm" as far as Btrfs stability goes, but apparently it's not just me who
uses it. In my experience 3.18 just works* and is very stable, and before that
it was 3.14, which by luck(?) happened to go longterm IIRC just before Btrfs
transitioned to "kernel worker threads" in 3.15 (and that caused ALL sorts of
trouble initially).
[*] at least in a relatively simple scenario -- with snapshots, but without
using any of the multi-device features or stuff such as qgroups or
send/receive.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-09-25 13:43 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 [this message]
[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
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=20150925184300.1d67254b@natsu \
--to=rm@romanrm.net \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=r-btrfs@thefreemanclan.net \
--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).