On 8/22/16 5:04 PM, Ronan Arraes Jardim Chagas wrote:
> Em Seg, 2016-08-22 às 14:49 -0600, Chris Murphy escreveu:
>> This is really weird. I'm running 4.7.0 (Fedora) and I'm not
>> experiencing problems, let alone this. What is this kernel's
>> provenance? Is it a plain mainline 4.7.0 that you built? I'm not
>> really sure what to recommend except maybe going back to 4.5.7 or
>> 4.6.7 as it's a production machine. Heck even 4.4.19 is OK for me in
>> this regard.
>>
> 
> Well, I'm using the default openSUSE kernel here. And I have been seen
> this errors for sometimes. When I reported it, I was using v4.6.1.
> Hence, I think the version of btrfs-progs is not the problem.

The openSUSE Tumbleweed kernel is effectively vanilla for btrfs.  The
4.6-based kernel had two btrfs patches, the crc32c implementation
publishing patch that landed in 4.7, and the super_operation callback
that lets us publish the per-root anon dev via stat().  The problem
you're encountering isn't due to our patches.

-Jeff

-- 
Jeff Mahoney
SUSE Labs

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to