Even without swap partition mounted the system crashed. Coming back with atop, it turns out that it was willing to write to a swap partition anyway (and I guess it crashed because there is no partition available just like it was crashing when the partition was there but it was full). This (*) is an example of what atop says for the period when the system crashed. This means that the system would like to commit 2.2GB of virtual memory (vmcom) having 0.0MB of swap partition (SWP tot) and a vmlim of 1.0GB (from man atop I read that 'vmlim' is by default swap size plus 50% of memory size, and that the committed space is the reserved virtual space for all allocations of private memory space for processes. The kernel only verifies whether the committed space exceeds the limit if strict overcommit handling is configured (i.e. if vm.overcommit_memory is 2, but in my case it is 0).
(*) MEM | tot 2.0G | free 74.4M | cache 1.4G | buff 24.6M | slab 35.8M | SWP | tot 0.0M | free 0.0M | | vmcom 2.2G | vmlim 1.0G | PAG | scan 37568 | stall 0 | | swin 0 | swout 0 | DSK | sda | busy 0% | read 188 | write 1436 | avio 1 ms | DSK | sdc | busy 0% | read 72 | write 9 | avio 13 ms | DSK | sdb | busy 0% | read 67 | write 9 | avio 1 ms | -- Kubuntu Jaunty KDE 4.2 very high memory usage https://bugs.launchpad.net/bugs/343714 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
