On Tue, Jan 5, 2016 at 7:50 AM, Duncan <1i5t5.dun...@cox.net> wrote:
>
> If however you mounted it degraded,rw at some point, then I'd say the bug
> is in wetware, as in that case, based on my understanding, it's working
> as intended. I was inclined to believe that was what happened based on
> t
Chris Murphy posted on Sun, 03 Jan 2016 14:33:40 -0700 as excerpted:
> kernel-4.4.0-0.rc6.git0.1.fc24.x86_64 btrfs-progs 4.3.1
>
> There was some copy pasting, hence /mnt/brick vs /mnt/brick2 confusion,
> but the volume was always cleanly mounted and umounted.
>
> The biggest problem I have with
kernel-4.4.0-0.rc6.git0.1.fc24.x86_64
btrfs-progs 4.3.1
There was some copy pasting, hence /mnt/brick vs /mnt/brick2
confusion, but the volume was always cleanly mounted and umounted.
The biggest problem I have with all of this is the completely silent
addition of single chunks. That made the vol
Chris Murphy posted on Sat, 02 Jan 2016 12:22:07 -0700 as excerpted:
> OK, I basically do not trust the f'n kernel anymore. I'm having to
> reboot in order to get to a (reasonably) deterministic state. Merely
> disconnecting devices doesn't make all aspects of that device and its
> filesystem, va
