From owner-freebsd-smp Tue Sep 19 12:50:54 2000 Delivered-To: freebsd-smp@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id E65DD37B422; Tue, 19 Sep 2000 12:50:50 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id VAA20798; Tue, 19 Sep 2000 21:49:54 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8JK9Ud00665; Tue, 19 Sep 2000 22:09:30 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Tue, 19 Sep 2000 22:09:30 +0200 (CEST) From: Michael Reifenberger To: Tor.Egge@fast.no Cc: root@nihil.plaut.de, grog@lemis.com, FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io In-Reply-To: <200009191829.UAA68967@midten.fast.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 19 Sep 2000 Tor.Egge@fast.no wrote: ... > This looks like you've hit the limit for the FFS node memory type. > > vmstat -m will indicate if this is correct. > ... > Increasing the kmem_map size (by setting a loader variable > (kern.vm.kmem.size) or defining VM_KMEM_SIZE and VM_KMEM_SIZE_MAX in > the kernel config file) should help. I'll try. Thanks for the hint! BTW: Is it possible to dynamically adjust the limit of the node mem? The system shouldn't freeze anyway. Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message