On Fri, Jul 1, 2016 at 7:47 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > This is too well trimmed. I'm not seeing the actual oops, can you trim > this less so it's possible to see what was going on a minute (or 10) > before this? I've updated the log[3]. There is no crash per se here, just the system becomes unresponsive. It looks like some watchdog timer goes off (NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s!) and it becomes usable again for a few seconds before it locks up again and the process repeats. > > About how many subvolumes? 100, maybe more. The full story here is that my file system was becoming full so I was using baobab to investigate what was eating my storage. While baobab was scanning my disk, I happened to be deleting a few things and running `btrfs balance start...` (as you can see in[3]), but I don't think the lockups are related to any of that because I saw them previously with baobab when I was not doing any balance. I've since removed all of the btrfs subvolumes created by docker and everything is working fine again with no lockups (so I can't recreate this anymore). ¬grey [3]: https://gist.github.com/greyltc/5a9198f402e4e9b9895af0b2a3ead375 -- 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
