2015-08-19 17:39 GMT+02:00 Leo Unbekandt <leo.unbek@xxxxxxxxx>: > Hello everyone, > > I've encountered what looks like a nasty bug which occures when the OOM > kills a process and that this process is working with the file system. > I've been able to reproduce this issue using docker, by limiting the > memory limits of process and make them crash when working. > > (You can find more information there: my post on Docker bug tracker, but > it seems that it is more a BTRF-related issue > https://github.com/docker/docker/issues/15654#issuecomment-132384763) > > Once the processes have been killed, a BTRFS kworker switched in > uninterruptible (state D) IO wait, and the file system is completely > unusable, no way to read or write from it which is pretty critical, in > my case Docker is not usable anymore as btrfs is the used storage backend. > > OOM logs: http://pastebin.com/Lb4Gybay (Simple OOM logs) > BTRFS freeze and uninterruptible processes (plus Sysrq-w): > http://pastebin.com/qd1yB8u2 > > Hoping that I've got enough information, tell me if you need more. Now > I'm able to reproduce quite easily. Just a heads up - I'm just a user but I've seen exactly the same problem (running Java apps like Elasticsearch/Hadoop) when the OOM killer is triggered. Looks like you are using Linux 3.19 - but I've seen the issue also on 4.0 and 4.1. regards Martin -- 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
