Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #227315
| From | Pariksheet Nanda <pariksheet.nanda@protonmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: OOM-killer not being involked under memory pressure |
| Date | 2020-09-25 02:10 +0200 |
| Message-ID | <ASJtg-1pG-3@gated-at.bofh.it> (permalink) |
| References | <ASBvH-4O9-5@gated-at.bofh.it> <ASDQR-6kL-3@gated-at.bofh.it> <ASJ0d-10P-7@gated-at.bofh.it> <ASJjz-179-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> I just checked my other server which has ZFS on root without encryption, and see that I did not enable swap at all on that machine. So I'll disable swap, thrash the RAM with`stress`, and then hopefully the OOM-killer works like it does on that machine. Yay! Indeed disabling swap allowed the OOM-killer to work. Pariksheet $ sudo swapoff -av swapoff /dev/zd0 $ stress -m 4 --vm-bytes 2000M stress: info: [16295] dispatching hogs: 0 cpu, 0 io, 4 vm, 0 hdd stress: FAIL: [16295] (415) <-- worker 16299 got signal 9 stress: WARN: [16295] (417) now reaping child worker processes stress: FAIL: [16295] (451) failed run completed in 2s $ sudo journalctl -rt kernel | head -- Logs begin at Tue 2020-06-23 13:23:36 EDT, end at Thu 2020-09-24 20:06:09 EDT. -- Sep 24 20:02:12 xm1 kernel: oom_reaper: reaped process 16838 (stress), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB Sep 24 20:02:12 xm1 kernel: Killed process 16838 (stress) total-vm:2051852kB, anon-rss:1345260kB, file-rss:0kB, shmem-rss:0kB Sep 24 20:02:12 xm1 kernel: Out of memory: Kill process 16838 (stress) score 166 or sacrifice child Sep 24 20:02:12 xm1 kernel: [ 16840] 0 16840 1143 39 53248 0 0 nc Sep 24 20:02:12 xm1 kernel: [ 16839] 1000 16839 512963 323517 2637824 0 0 stress Sep 24 20:02:12 xm1 kernel: [ 16838] 1000 16838 512963 336315 2740224 0 0 stress Sep 24 20:02:12 xm1 kernel: [ 16837] 1000 16837 512963 308763 2523136 0 0 stress Sep 24 20:02:12 xm1 kernel: [ 16836] 1000 16836 512963 313283 2555904 0 0 stress Sep 24 20:02:12 xm1 kernel: [ 16835] 1000 16835 962 20 40960 0 0 stress
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
OOM-killer not being involked under memory pressure Pariksheet Nanda <pariksheet.nanda@protonmail.com> - 2020-09-24 17:40 +0200
Re: OOM-killer not being involked under memory pressure Stefan Monnier <monnier@iro.umontreal.ca> - 2020-09-24 20:10 +0200
Re: OOM-killer not being involked under memory pressure Pariksheet Nanda <pariksheet.nanda@protonmail.com> - 2020-09-25 01:40 +0200
Re: OOM-killer not being involked under memory pressure Pariksheet Nanda <pariksheet.nanda@protonmail.com> - 2020-09-25 02:00 +0200
Re: OOM-killer not being involked under memory pressure Pariksheet Nanda <pariksheet.nanda@protonmail.com> - 2020-09-25 02:10 +0200
Re: OOM-killer not being involked under memory pressure Linux-Fan <Ma_Sys.ma@web.de> - 2020-09-25 03:00 +0200
Re: OOM-killer not being involked under memory pressure Pariksheet Nanda <pariksheet.nanda@protonmail.com> - 2020-09-25 21:20 +0200
Re: OOM-killer not being involked under memory pressure Charles Curley <charlescurley@charlescurley.com> - 2020-09-25 15:50 +0200
Re: OOM-killer not being involked under memory pressure Tixy <tixy@yxit.co.uk> - 2020-09-25 18:30 +0200
Re: OOM-killer not being involked under memory pressure Brian <ad44@cityscape.co.uk> - 2020-09-25 20:10 +0200
Re: OOM-killer not being involked under memory pressure David Wright <deblis@lionunicorn.co.uk> - 2020-09-26 04:50 +0200
Re: OOM-killer not being involked under memory pressure Stefan Monnier <monnier@iro.umontreal.ca> - 2020-09-25 03:50 +0200
Re: OOM-killer not being involked under memory pressure Pariksheet Nanda <pariksheet.nanda@protonmail.com> - 2020-09-25 21:40 +0200
csiph-web