On 08/09/2016 01:27 PM, Hugo Mills wrote:
Over the weekend, I started doing some maintenance on my server: I upgraded to 4.7.0, and I started deleting a device from my array, preparatory to putting in a larger one. About halfway through the operation, several kernel threads hung up for a while (resulting in "blocked for 120s" messages), and then the delete process seems to have stopped entirely, although several kernel threads are at maximum usage. After a few hours, I rebooted the machine, and left it for a day or so. I tried the delete again this afternoon, and it's done the same thing again. The full log is included below. I have a kworker and a btrfs-transaction pegged at close to 100% of a core each, and a btrfs-cleaner (and the btrfs dev del process) in D state. The FS was not under load at the time of the failure, and it passes scrub. I haven't tried a btrfs check yet.
Thanks Hugo, can you nail down which line of code belongs to: btrfs_async_run_delayed_refs+0xc6 -chris -- 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
