Date: Thu, 6 May 2010 18:00:33 +0200 From: Ruben van Staveren <ruben@verweg.com> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Freebsd 8.0 kmem map too small Message-ID: <A1D01A64-AC7F-4C72-A489-D4855B27E547@verweg.com> In-Reply-To: <20100505133302.GB1626@garage.freebsd.pl> References: <4BDEA86E.3050109@zirakzigil.org> <20100503110100.GA93137@icarus.home.lan> <4BDEC106.3040807@zirakzigil.org> <4BE110E3.8040902@zirakzigil.org> <20100505075242.GA57550@icarus.home.lan> <4BE13067.1060606@zirakzigil.org> <20100505133302.GB1626@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 May 2010, at 15:33, Pawel Jakub Dawidek wrote: > Could you try to track down the commit that is causing your problems? > Could you try 8-STABLE kernel from before r206815? I do suspect something similar like that, and try to roll the kernel = back too. I was just fine with 8.0 with zfs-on-root till the last update when my = typical workload (portupgrade every now and then, make world) resulted = in kmem map too small panics and more sluggish performance (spending = most time in zio->io_cv) during pkgdb -F on a i386 system with 2gb = memory. I have 1gb memory sized amd64 vmware fusion vm's that run = without incident using the same workload. I had to bump KVA_PAGES to 512 and set vm.kmem_size=3D1024M to have this = i386 system stable again. Prior to that I tried to lower the arc cache = size but that resulted in a unresponsive system that I could not = diagnose. Regards, Ruben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A1D01A64-AC7F-4C72-A489-D4855B27E547>