>I would be really interesting to see what those tasks are blocked on.
Ok, i got it! Problem occurs two times and it behaves differently each time, I was running kernel with that latest patch. 1.) It doesn't have impact on the whole server, only on one cgroup. Here are stacks: http://watchdog.sk/lkml/memcg-bug-7.tar.gz 2.) It almost takes down the server because of huge I/O on HDDs. Unfortunately, i had a bug in my script which was suppose to gather stacks (i wasn't able to do it by hand like in (1), server was almost unoperable). But I was lucky and somehow killed processes from problematic cgroup (via htop) and server was ok again EXCEPT one important thing - processes from that cgroup were still running in D state and i wasn't able to kill them for good. They were taking web server network ports so i had to reboot the server :( BUT, before that, i gathered stacks: http://watchdog.sk/lkml/memcg-bug-8.tar.gz What do you think? azur -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
