From owner-freebsd-current Sun Apr 2 12: 7: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 3DB6D37BB18 for ; Sun, 2 Apr 2000 12:07:02 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id VAA29870; Sun, 2 Apr 2000 21:05:27 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id VAA30613; Sun, 2 Apr 2000 21:06:25 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id VAA25531; Sun, 2 Apr 2000 21:07:33 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 21:07:33 +0200 From: Bernd Walter To: Vallo Kallaste Cc: Bernd Walter , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402210733.A25516@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> <20000402173729.A25194@cicely8.cicely.de> <20000402200254.A69811@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402200254.A69811@myhakas.matti.ee>; from vallo@matti.ee on Sun, Apr 02, 2000 at 08:02:54PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 08:02:54PM +0200, Vallo Kallaste wrote: > Yes, but I don't have space for crashdump and I can't build new kernel > with limited memory usage because I don't have /usr filesystem up and > running. Is there a way to limit memory usage without recompiling > kernel? I can store 32MB crashdump at the moment, no separate /var > filesystem because I thought 4.0-RELEASE will be stable enough for > experimenting with vinum.. > I don't have another 4.0-RELEASE or stable system but I'll try to build > 4.0-R kernel on -current system. Just to clearify the things... Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message