From owner-freebsd-current Wed Jan 14 15:27:26 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14375 for current-outgoing; Wed, 14 Jan 1998 15:27:26 -0800 (PST) (envelope-from owner-freebsd-current) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13616 for ; Wed, 14 Jan 1998 15:20:07 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA08559; Wed, 14 Jan 1998 15:23:38 -0800 (PST) Message-Id: <199801142323.PAA08559@implode.root.com> To: shimon@simon-shapiro.org cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic: kmem_malloc: kmem_map too small In-reply-to: Your message of "Wed, 14 Jan 1998 12:27:34 PST." From: David Greenman Reply-To: dg@root.com Date: Wed, 14 Jan 1998 15:23:38 -0800 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On 13-Jan-98 David Greenman wrote: >>> vnodes145070 24237K 24237K 39322K 246196 0 0 16,32,256 >> >> Huh - 145070 vnodes? How much physical memory is in this machine? I >> have >> a gigabyte of RAM in wcarchive and it peaks at about 87,000. This looks >> like >> a vnode leak to me. Which version of FreeBSD is this? > >384MB or RAM. 3.0-current as of 12-Jan. > >What do I do about the vnode leak? I guess you wait until John has fixed the leak - I'm pretty sure this is one of the recent bugs that he's been working on resolving. >The way to trigger it is to cd into one LARGE directory and do >``find . | cpio -dmpv /Destination'' > > >>>Memory Totals: In Use Free Requests >>> 57971K 554K 4718664 > >I have seen the FREE go down to 38K or so. "Free" doesn't matter; ignore that. >> ...no surprise that the machine is panicing. > >Dumb Question: Which is the alert and why? "In Use" is in outer space. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project