kmem_malloc(4096): kmem_map too small: 536870912 total allocated
Vladimir Sharun
sharun at ukr.net
Tue Oct 25 04:57:18 PDT 2005
I found the sources of the leak: if exim accessess ANY configuration/text
files over NFS, there will be leak. And, how often exim will be called, then
quicker your system dies.
My main problem now is to build near-realtime mirroring solution nfs-to-local
for around 20 files (up to 1Mb everything). Any /ports solution ?
The next question to Philip Hazel: any comments why this happens ?
Vladimir Sharun wrote:
VS> We have 2xOpteron/2Gb RAM server with extensive disk load. Every week or two
VS> it suddenly hangs with "kmem_malloc(4096): kmem_map too small 335bla-bla allocated".
VS> I look onto handbook and put vm.kmem_size_max="536870912" onto /boot/loader.conf.
VS> Today was the same with the new parameters. Is there any other solutions ?
VS> # sysctl -a | grep kmem
VS> vm.kmem_size: 536870912
VS> vm.kmem_size_max: 536870912
VS> vm.kmem_size_scale: 3
VS> The only vm.kmem_size_max on loader.conf, no vm.kmem_size.
VS> We're running FreeBSD 6.0-BETA5 #0: Wed Sep 28 16:54:33 EEST 2005
VS> in i386 mode. The same was with 5.3/5.4 and NetBSD 2.0 on this machine.
More information about the freebsd-stable
mailing list