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
pgpbBIVeVhYn4.pgp
Description: PGP signature
