linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Opps.. Should be 4.9/4.10 Experiences
Date: Fri, 17 Feb 2017 08:04:55 -0500	[thread overview]
Message-ID: <ec42604a-7d25-4fa9-3966-e87004f74df9@gmail.com> (raw)
In-Reply-To: <pan$1fe63$b02c9dfa$efbc9dc2$1ccd0342@cox.net>

On 2017-02-17 03:26, Duncan wrote:
> Imran Geriskovan posted on Thu, 16 Feb 2017 13:42:09 +0200 as excerpted:
>
>> Opps.. I mean 4.9/4.10 Experiences
>>
>> On 2/16/17, 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?
>
> I ran 4.9 and have been on 4.10 since before rc1.  Btrfs has been fine
> here, tho there have been some late rc7/8 fixes.  I've had and still have
> some 4.10 issues, but they're amdgpu, not btrfs related.  (Unfortunately,
> between working long hours and being sick partly as a result, I've had
> little time to report them, but booting with amdgpu.dpm=0 has let me
> continue running 4.10-git, tho I don't know exactly why if I'm not going
> to have time to report problems anyway.)
>
FWIW, I've had largely similar experiences since about 4.0.  I'm also 
not using anything more complicated than raid1/raid0, and I stay on top 
of monitoring for all my systems, but even accounting for that, I've had 
no BTRFS issues that caused anything beyond minor inconvenience (that 
is, no data loss, nothing that would have required taking the system 
completely off-line to fix if it was the root filesystem, and no crashes 
arising from BTRFS itself).

 From what I've seen though, as long as you stay up to date and don't do 
much more complicated than a raid1 or raid0 setup, don't use qgroups 
(they're technically working, but they still have a significant 
performance impact) and don't use lots of snapshots, you should be 
relatively fine.

      reply	other threads:[~2017-02-17 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 11:42 Opps.. Should be 4.9/4.10 Experiences Imran Geriskovan
2017-02-17  8:26 ` Duncan
2017-02-17 13:04   ` Austin S. Hemmelgarn [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=ec42604a-7d25-4fa9-3966-e87004f74df9@gmail.com \
    --to=ahferroin7@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).