From owner-freebsd-current Sat Sep 23 4: 8:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 6AFCA37B422 for ; Sat, 23 Sep 2000 04:08:10 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id NAA54308; Sat, 23 Sep 2000 13:07:36 +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 e8NB7KM00965; Sat, 23 Sep 2000 13:07:20 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sat, 23 Sep 2000 13:07:20 +0200 (CEST) From: Michael Reifenberger To: Kenneth Wayne Culver Cc: Michael Reifenberger , freebsd-current@FreeBSD.ORG Subject: Re: -CURRENT crashes under heavy disk activity In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Sep 2000, Kenneth Wayne Culver wrote: ... > Alright, I think I may just do that too... I was going to try to tough it > out... but it looks like that just won't work.... I wish there was some Thats not correct. You have to upper kern.vm.kmem.size as a workaround. Please read the thread for more information. BTW: The increased memoryconsumption (and leak?) looks like a bug to me. Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message