From owner-freebsd-stable@FreeBSD.ORG  Tue Jul 29 15:23:10 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5828737B401; Tue, 29 Jul 2003 15:23:10 -0700 (PDT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5AC7E43F85; Tue, 29 Jul 2003 15:23:09 -0700 (PDT)
	(envelope-from don@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19)
	id <305LG0JJ>; Tue, 29 Jul 2003 18:23:08 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C8533702742061@mail.sandvine.com>
From: Don Bowman <don@sandvine.com>
To: 'Robert Watson' <rwatson@freebsd.org>,
	Dave Dolson <ddolson@sandvine.com>
Date: Tue, 29 Jul 2003 18:23:05 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
cc: "'freebsd-stable@freebsd.org'" <freebsd-stable@freebsd.org>
Subject: RE: kernel deadlock
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 22:23:10 -0000

From: Robert Watson [mailto:rwatson@freebsd.org]
> On Tue, 29 Jul 2003, Dave Dolson wrote:
> 
> > To follow up, I've discovered that the system has exhausted its "FFS
> > node" malloc type. 
 ...
> 
> Some problems with this have turned up in -CURRENT on large-memory
> machines where some of the scaling factors have been off.  In 

We currently have kern.maxvnodes=70354 set (automatically scaled). This
is a 1GB box.

I will try re-running the test with less.

when it hits kern.maxvnodes, what will it do?

--don