From owner-freebsd-stable@FreeBSD.ORG Tue Feb 27 20:54:14 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3EA3016A401 for ; Tue, 27 Feb 2007 20:54:14 +0000 (UTC) (envelope-from kozlov@ravenloft.kiev.ua) Received: from istc.kiev.ua (wolf.istc.kiev.ua [193.108.236.1]) by mx1.freebsd.org (Postfix) with ESMTP id DADE513C4B5 for ; Tue, 27 Feb 2007 20:54:13 +0000 (UTC) (envelope-from kozlov@ravenloft.kiev.ua) Received: from localhost ([127.0.0.1] helo=ravenloft.kiev.ua) by istc.kiev.ua with esmtp (Exim 4.52) id 1HM9Ku-000707-6q; Tue, 27 Feb 2007 22:54:12 +0200 Received: from kozlov by ravenloft.kiev.ua with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1HM9KZ-000ItM-D4; Tue, 27 Feb 2007 22:53:51 +0200 Date: Tue, 27 Feb 2007 22:53:51 +0200 From: Alex Kozlov To: Mikhail Teterin Message-ID: <20070227205351.GA72597@ravenloft.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Sender: Alex Kozlov X-Spam-Score: 0.0 (/) X-Spam-Report: Content analysis detailz: (0.0 points, 10.0 required) Cc: stable@freebsd.org Subject: Re: panic: kmem_malloc(16384): kmem_map too small: md-mounted /tmp filled up X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 20:54:14 -0000 On Tue, Feb 27, 2007 at 02:48:11PM -0500, Mikhail Teterin wrote: > On Tuesday 27 February 2007 11:41, Alex Kozlov wrote: > = On Tue, Feb 27, 2007 at 10:59:08AM -0500, Mikhail Teterin wrote: > = > /tmp's space allocation (after reboot) is as follows: > = > > = > Filesystem 1K-blocks Used Avail Capacity Mounted on > = > /dev/md0 2026030 3552 1860396 0% /tmp > = > > = > Note, that it is supposed to hold 2Gb, but was filled up and paniced > = > holding about 300Mb... Probably, because it is created with ``-M'' > = > by default -- but it is not supposed to panic anyway! > = You may want to set -o reserve option. Or better, switch to a swap backed > = md. > > Yes, I switched to swap-backed md already. But the malloc-based variety is > currently the _default_ (see /etc/defaults/rc.conf)... Bad default. Anyway, you may wish to change tmpmfs_flags on something like that: "-S -m0 -o async,nosymfollow,nosuid" > Creation of a 2Gb malloc-based md should've failed on a machine with 768Mb of > RAM, shouldn't it have? Only if you set '-o reserve'. Memory for malloc-based md was allocated dynamically. -- Adios