Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Aug 2007 10:32:45 +0300
From:      Stefan Lambrev <stefan.lambrev@moneybookers.com>
To:        Eric Kjeldergaard <kjelderg@gmail.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: kernel panic with memory disks
Message-ID:  <46CA951D.1060303@moneybookers.com>
In-Reply-To: <d9175cad0708201058o62e4441cq6c5a524791d65c4d@mail.gmail.com>
References:  <46C9B99C.1060403@moneybookers.com> <d9175cad0708201058o62e4441cq6c5a524791d65c4d@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello,

Eric Kjeldergaard wrote:
> On 20/08/07, Stefan Lambrev <stefan.lambrev@moneybookers.com> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46CA951D.1060303>