On Fri, Dec 2, 2016 at 1:36 PM, Blake Lewis wrote:
> Well, 3.10 is what you get with the RHEL7.x distributions, so that's
> why people are running it.
> Apparently, it is "good enough" for many purposes.
Nope. Btrfs in RHEL 7 is a technology preview, and ...
"Technology
Thanks, Duncan. Your points are very reasonable and I will be doing
a bisect, as you suggest (though I don't know that the problem is fixed
in later releases, just that we couldn't reproduce it readily). Just to be
clear, I am not looking for support. I just hoped that perhaps this had
been a
Blake Lewis posted on Fri, 02 Dec 2016 12:36:29 -0800 as excerpted:
> Well, 3.10 is what you get with the RHEL7.x distributions, so that's why
> people are running it.
> Apparently, it is "good enough" for many purposes.
>
> My real goal here is to understand the scope of the bug and whether any
Well, 3.10 is what you get with the RHEL7.x distributions, so that's
why people are running it.
Apparently, it is "good enough" for many purposes.
My real goal here is to understand the scope of the bug and whether
any mitigation is
possible. Of course, I don't expect anyone else to make a patch
Hi,
Le 02/12/2016 à 20:07, Blake Lewis a écrit :
> Hi, all, this is my first posting to the mailing list. I am a
> long-time file system guy who is just starting to take a serious
> interest in btrfs.
>
> My company's product uses btrfs for its backing storage. We
> maintain a log file to let
Hi, all, this is my first posting to the mailing list. I am a
long-time file system guy who is just starting to take a serious
interest in btrfs.
My company's product uses btrfs for its backing storage. We
maintain a log file to let us synchronize after reboots. In
testing, we find that when