From owner-freebsd-questions@FreeBSD.ORG Tue Jun 3 15:00:25 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 760CB1065673 for ; Tue, 3 Jun 2008 15:00:25 +0000 (UTC) (envelope-from fbsd06+WR=5e652d97@mlists.homeunix.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id 4CB8A8FC13 for ; Tue, 3 Jun 2008 15:00:25 +0000 (UTC) (envelope-from fbsd06+WR=5e652d97@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by turtle-in.mxes.net (Postfix) with ESMTP id 637A7164695 for ; Tue, 3 Jun 2008 10:43:56 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 9851B23E4AB; Tue, 3 Jun 2008 10:43:54 -0400 (EDT) Date: Tue, 3 Jun 2008 15:43:51 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080603154351.40abb46f@gumby.homeunix.com.> In-Reply-To: References: X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: The Ghost Subject: Re: very strange reaction of the md disks X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2008 15:00:25 -0000 On Tue, 03 Jun 2008 11:31:05 +0400 The Ghost wrote: > Hello, > > Maybe I just don't understand something, but anyway, it looks really > odd. > > I have a machine with 2 Gb RAM with a clean newly-installed > FREEBSD-7.0-RELEASE. I make two 300-MB mdconfig disks and populate > them, and when the first one was already full and the second one is > only half-full, I get a kernel panic "not enough memory". I wonder > where did 1,5 Gb go?? Try using swap-backed md devices instead. With both malloc and swap devices the data is stored in ram and paged-out to swap as needed, but it helps with some of the malloc limitations. I'm using a 2.7GB /tmp directory with 1.6GB of ram and have not had any problems. I don't actually see any swap usage unless I put a lot of data on the device, otherwise I can even do a swapoff.