On 19.04.2017 16:04, Carlos Maiolino wrote: > If I am not blind, the task currently owning the cpu isn't listed there, which I > suppose to be already running. Correct, the only process utilizing the CPU is xfsaild. It is also the only process doing I/O, and it looks like it's doing only reads. It (xfsaild) never shows up in dmesg as blocked. > Next time you hit it, could you please paste the stack trace of the task owning > the cpu? Which I suppose to be xfsaild according to your report. > > A simple `cat /proc/<pid>/stack` is probably enough Sure, will do. -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
