From owner-freebsd-current@FreeBSD.ORG Tue Feb 24 07:06:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FA6D16A4CE for ; Tue, 24 Feb 2004 07:06:24 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ABFE43D1F for ; Tue, 24 Feb 2004 07:06:24 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) i1OF6HNv013707; Tue, 24 Feb 2004 10:06:17 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i1OF6G9V013704; Tue, 24 Feb 2004 10:06:17 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Tue, 24 Feb 2004 10:06:16 -0500 (EST) From: Andre Guibert de Bruet To: Leroy van Logchem In-Reply-To: <403B2F09.8060207@wldelft.nl> Message-ID: <20040224100432.D3751@alpha.siliconlandmark.com> References: <403B2F09.8060207@wldelft.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 5.2.1-RC2 panic: kmem_malloc(4096): kmem_map too small X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 24 Feb 2004 15:06:24 -0000 On Tue, 24 Feb 2004, Leroy van Logchem wrote: > Best mailinglist, > > Short: > > I'am having panics while transfering alot of files using NFS (as client). > > Long: > > After succesfull synchronization of two complete filesystems using NFS > v3 (udp) I restarted the ssync after couple of hours idle time and got: > > panic: kmem_malloc(4096): kmem_map too small Leroy, You're running out of kmem. Try the following kernel options: options VM_KMEM_SIZE_MAX=(768*1048576) options VM_KMEM_SIZE_SCALE=2 If you want to know what these mean/do, search the mailing list. Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >