From owner-freebsd-current Sun Apr 2 12:12:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2917037BE30 for ; Sun, 2 Apr 2000 12:12:53 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA67427; Sun, 2 Apr 2000 21:12:45 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004021912.VAA67427@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000402210733.A25516@cicely8.cicely.de> from Bernd Walter at "Apr 2, 2000 09:07:33 pm" To: ticso@cicely.de (Bernd Walter) Date: Sun, 2 Apr 2000 21:12:45 +0200 (CEST) Cc: vallo@matti.ee (Vallo Kallaste), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bernd Walter wrote: > 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? I have the problem with 4.0-RELEASE, STABLE and 5.0-current but it might only occur with RAID5... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message