From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 07:32:47 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B5FC16A417 for ; Tue, 21 Aug 2007 07:32:47 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id A5B1613C457 for ; Tue, 21 Aug 2007 07:32:46 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id EEB5E1B10EA4; Tue, 21 Aug 2007 09:32:44 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id EB64B1B10E0D; Tue, 21 Aug 2007 09:32:44 +0200 (CEST) Message-ID: <46CA951D.1060303@moneybookers.com> Date: Tue, 21 Aug 2007 10:32:45 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.4pre (X11/20070711) MIME-Version: 1.0 To: Eric Kjeldergaard References: <46C9B99C.1060403@moneybookers.com> In-Reply-To: Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: freebsd-current@freebsd.org Subject: Re: kernel panic with memory disks 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, 21 Aug 2007 07:32:47 -0000 Hello, Eric Kjeldergaard wrote: > On 20/08/07, Stefan Lambrev wrote: > >> Hello, >> >> I do not know if this is know behavior, and I know that 6.2 panic if the >> memory disk got full, >> but on 7-current the panic is before the disk got full. >> >> Here is what I do: >> >> mdconfig -a -t malloc -s 800m >> newfs /dev/md0 >> mount /dev/md0 /mnt >> cp 600mb.file /mnt >> > > -t type > Select the type of the memory disk. > > malloc Storage for this type of memory disk is allocated with > malloc(9). This limits the size to the malloc bucket > limit in the kernel. If the -o reserve option is not > set, creating and filling a large malloc-backed memory > disk is a very easy way to panic a system. > -- mdconfig(8) > > I really should read manuals more carefully :) Thanks for the information. Just one more question - to prevent panic I should use "-o reserve" and have to increase: vfs.maxmallocbufspace vfs.bufmallocspace -- Best Wishes, Stefan Lambrev ICQ# 24134177