From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Opps.. Should be 4.9/4.10 Experiences
Date: Fri, 17 Feb 2017 08:26:15 +0000 (UTC) [thread overview]
Message-ID: <pan$1fe63$b02c9dfa$efbc9dc2$1ccd0342@cox.net> (raw)
In-Reply-To: CAK5rZE7mDy+8hkm74UVS81Xht=QxvNOmW=ZfYqpHmnqGZHbMbA@mail.gmail.com
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.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-02-17 8:26 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 [this message]
2017-02-17 13:04 ` Austin S. Hemmelgarn
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='pan$1fe63$b02c9dfa$efbc9dc2$1ccd0342@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.