On 08/08/2016 05:16 PM, Chris Mason wrote: > > Fantastic, thanks again for digging through it. Making the patch is > much easier than testing the patch in this case. If you can trigger > this semi-reliably, we can add some debugging to make sure we're not > papering over some other problem.
I don;'t have a reproducer per-se, but I have a fair number of servers, whose workload causes the issue, so if I patch btrfs and apply it to 5-10 server I;d expect at least one of them to show what the real issue is. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
