From owner-freebsd-fs@FreeBSD.ORG Wed May 5 14:39:53 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 54EB01065673 for ; Wed, 5 May 2010 14:39:53 +0000 (UTC) (envelope-from ben@wanderview.com) Received: from mail.wanderview.com (mail.wanderview.com [66.92.166.102]) by mx1.freebsd.org (Postfix) with ESMTP id 631AA8FC13 for ; Wed, 5 May 2010 14:39:51 +0000 (UTC) Received: from xykon.in.wanderview.com (xykon.in.wanderview.com [10.76.10.152]) (authenticated bits=0) by mail.wanderview.com (8.14.4/8.14.4) with ESMTP id o45ECnqS027944 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 May 2010 14:12:49 GMT (envelope-from ben@wanderview.com) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Ben Kelly In-Reply-To: <20100505133302.GB1626@garage.freebsd.pl> Date: Wed, 5 May 2010 10:12:49 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <533152DA-3B2F-4994-9206-727A2B0010AD@wanderview.com> 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> To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.1078) X-Spam-Score: -1.01 () ALL_TRUSTED,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.67 on 10.76.20.1 Cc: freebsd-fs@freebsd.org, FreeBSD Stable Subject: Re: Freebsd 8.0 kmem map too small X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 May 2010 14:39:53 -0000 On May 5, 2010, at 9:33 AM, Pawel Jakub Dawidek wrote: > On Wed, May 05, 2010 at 10:46:31AM +0200, Giulio Ferro wrote: >> On 05.05.2010 09:52, Jeremy Chadwick wrote: >>=20 >> Nope, it's happened again... Now I've tried to rise vm.kmem_size to = 6G... >>=20 >>=20 >>> Did you set both vm.kmem_size and vfs.zfs.arc_max, setting the = latter to >>> something *less* than vm.kmem_size? >>>=20 >>>=20 >>=20 >> Yes. >> After your suggestion, I set >> vfs.zfs.arc_max: 3758096384 >> vm.kmem_size: 4G >>=20 >> Now: >> vfs.zfs.arc_max: 3758096384 >> vm.kmem_size: 6392119296 >=20 > Could you try to track down the commit that is causing your problems? > Could you try 8-STABLE kernel from before r206815? Are others generally able to run ARC values so close to kmem size? My = experience has been that you really need the ARC to be much smaller than = the kmem limit (like 25% or less) due to fragmentation of kmem_map. - Ben=