Date: Mon, 24 Oct 2005 15:53:43 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Vladimir Sharun <sharun@ukr.net>, freebsd-stable@freebsd.org Subject: Re: kmem_malloc(4096): kmem_map too small: 536870912 total allocated Message-ID: <20051024195343.GA64734@xor.obsecurity.org> In-Reply-To: <20051023170709.GA99337@dun.ukr.net> References: <20051023074342.GA97095@dun.ukr.net> <20051023080622.GA76867@xor.obsecurity.org> <20051023082110.GA97329@dun.ukr.net> <20051023082948.GA90034@xor.obsecurity.org> <20051023170709.GA99337@dun.ukr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Sun, Oct 23, 2005 at 08:07:09PM +0300, Vladimir Sharun wrote: > Kris Kennaway wrote: > > >>> We have 2xOpteron/2Gb RAM server with extrensive disk load. Every week or two > > >>> it suddenly hangs with "kmem_malloc(4096): kmem_map too small 335bla-bla allocated". > > >>> I look onto handbook and put vm.kmem_size_max="536870912" onto /boot/loader.conf. > > >>> Today was the same with the new parameters. Is there any other solutions ? > >> > > KK>> If that's not enough, try making it larger. > >> > >> On what size we can be sure, that "that's enough" ? > > KK> It depends on your workload, so keep increasing it until the problem > KK> stops or you discover that you need more RAM to handle your workload. > > Looks like kernel leak (thanks for tip to Gleb Smirnov) in lockf. > # vmstat -zm | grep lock > lockf 2257779 70556K - 19476940 32,64 > ... and keep raising. > > That's another one machine with 1Gb RAM, having 512M for vm.kmem_size_max too. OK, what version was this again? Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDXTvHWry0BWjoQKURAusAAJ4pF4sA4/EkJmIeteVL5cgEITRAVwCePdC5 7/cIqUvwvsK6/lqJ+7gY+7U= =R3Zc -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051024195343.GA64734>