Messages in this thread | | | Date | Mon, 2 May 2011 12:59:50 -0700 (PDT) | From | Christian Kujau <> | Subject | Re: 2.6.39-rc4+: oom-killer busy killing tasks |
| |
On Mon, 2 May 2011 at 22:19, Dave Chinner wrote: > Yes. Try 2 orders of magnitude as a start. i.e change it to 10000...
I've run the -12 test with vfs_cache_pressure=200 and now the -13 test with vfs_cache_pressure=10000. The OOM killer still kicks in, but the machine seems to be more usable afterwards and does not get totally stuck:
http://nerdbynature.de/bits/2.6.39-rc4/oom/ - messages-12.txt.gz & slabinfo-12.txt.bz2 * oom-debug.sh invoked oom-killer at 01:27:11 * sysrq-w works until 01:27:08, but got killed by oom
- messages-13.txt.gz & slabinfo-13.txt.bz2 * find invoked oom-killer at 08:44:07 * sysrq-w works until 08:45:48 (listing jbd2/hda6-8), then my debug script got killed
Thanks, Christian. -- BOFH excuse #224:
Jan 9 16:41:27 huber su: 'su root' succeeded for .... on /dev/pts/1
| |