Error messages in dmesg |tail are still ongoing, presumably originating from the btrfs command which still is eating 100% of the cpu,
I did not reboot yet nor kill the btrfs process (pid 27516).
Here's two lines from two of the latest error messages in dmesg:
[3111643.576434] [<ffffffff817bc3b2>] entry_SYSCALL_64_fastpath+0x16/0x75
[3111671.589435] [<ffffffff817bc3b2>] entry_SYSCALL_64_fastpath+0x16/0x75
so the time interval beween two messages is about 28 seconds.
Error messages in dmesg |tail are still ongoing, presumably originating from the btrfs command which still is eating 100% of the cpu,
I did not reboot yet nor kill the btrfs process (pid 27516).
Here's two lines from two of the latest error messages in dmesg: 3b2>] entry_SYSCALL_ 64_fastpath+ 0x16/0x75 3b2>] entry_SYSCALL_ 64_fastpath+ 0x16/0x75
[3111643.576434] [<ffffffff817bc
[3111671.589435] [<ffffffff817bc
so the time interval beween two messages is about 28 seconds.