On 07/12/2018 07:07 PM, Pete wrote: > On 07/12/2018 08:11 AM, Nikolay Borisov wrote: >> >> >> This one shouldn't have gone RO since it has plenty of unallocated and >> free space. What was the workload at the time it went RO? Hard to say, >> it's best if you can provide output with the debug patch applied when >> this issue re-appears. >> > > I'll respond in a separate email to list, as the above is the more > important issue and I need to trawl the logs. Nothing seen, though I recently had the disks go read-only. I'll wait and see what happens. Pete -- 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
