On Thu 25-06-15 14:43:42, Nikolay Borisov wrote: > I do have several OOM reports unfortunately I don't think I can > correlate them in any sensible way to be able to answer the question > "Which was the process that was writing prior to the D state occuring". > Maybe you can be more specific as to what am I likely looking for? Is the system still in this state? If yes I would check the last few OOM reports which will tell you the pid of the oom victim and then I would check sysrq+t whether they are still alive. And if yes check their stack traces to see whether they are still in the allocation path or they got stuck somewhere else or maybe they are not related at all... sysrq+t might be useful even when this is not oom related because it can pinpoint the task which is blocking your waiters. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
