From owner-freebsd-current@FreeBSD.ORG Tue May 19 02:16:05 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67E9B1065677; Tue, 19 May 2009 02:16:05 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id 374398FC0A; Tue, 19 May 2009 02:16:04 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from localhost (localhost [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id 64F5271F41F; Mon, 18 May 2009 22:16:04 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ubwcatAi8avH; Mon, 18 May 2009 22:16:04 -0400 (EDT) Received: from localhost (daemon.egr.msu.edu [35.9.44.65]) by mx.egr.msu.edu (Postfix) with ESMTP id 1D24671F41E; Mon, 18 May 2009 22:16:04 -0400 (EDT) Received: by localhost (Postfix, from userid 21281) id 0BB97745; Mon, 18 May 2009 22:16:04 -0400 (EDT) Date: Mon, 18 May 2009 22:16:04 -0400 From: Adam McDougall To: Kip Macy Message-ID: <20090519021603.GT82547@egr.msu.edu> References: <20090518145614.GF82547@egr.msu.edu> <3c1674c90905181659g1d20f0f1w3f623966ae4440ec@mail.gmail.com> <20090519012202.GR82547@egr.msu.edu> <3c1674c90905181826p787a346cie90429324444a9c4@mail.gmail.com> <20090519015713.GS82547@egr.msu.edu> <3c1674c90905181903o281406fbia135c295738d73b5@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3c1674c90905181903o281406fbia135c295738d73b5@mail.gmail.com> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: current@freebsd.org, Larry Rosenman Subject: Re: Fatal trap 12: page fault panic with recent kernel with ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 02:16:05 -0000 On Mon, May 18, 2009 at 07:03:45PM -0700, Kip Macy wrote: > Thanks, I appreciate all this work. ?Not allowing inactive pages to > shrink the ARC sounds great as an option. ?I would be willing to bet > that allowing inactive pages to shrink the arc would be far less > detrimental to most people who aren't running a constant busy file > server load, and its definitely important to try to protect untuned > boxes. Allowing NFS to use ARC buffers might be one solution to that. That would be interesting. I haven't used ZFS for any NFS serving yet though. With my mix of userspace file serving daemons my Inactive mem just rises 1-3M/sec until almost all free memory is consumed and I don't know why. None of the processes in top or ps can account for 16G of Inactive. > Do you have any suggestions for increasing the amount of memory ARC > can use? ?I've had difficulty increasing kmem past a few gigs on any > of my recent builds (all past where kmem was changed so it could be > more than ~2g) because at some point the kernel would stop booting. > If I increase them too far, a few lines of the booting kernel would > print, followed by a long stream of page fault panics or something > with a sudden reboot. ?With the recent change allowing the use of > direct mem, the ARC could easily use ample memory except it turned > out not to be stable. As of r192216 that should not be a probably any more. The maximum kmem is now 512GB. It will be at least a year or two before anyone bumps his head against that. Ahh oops, I mistakenly thought it was backed out a few minutes ago but that was something else. I guess that gives me something else I can test. A number of changes went in recently and it was hard to tell which commits were causing which symptoms.