Latest update on this thread. btrfs check (4.3.1) reports no problems. Volume mounts with kernel 4.2.8 with no errors. And I just did a scrub and there were no errors, not even any fix up messages. And dev stats are all zero. So... it appears it was a minor enough problem, and still consistent enough, that it fixed itself. Granted, there was no writing occurring at the time, just heavy reading, or perhaps this would be a different story. Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
