From owner-freebsd-stable Fri Jan 5 15:49:56 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 15:49:54 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id E4E6E37B400 for ; Fri, 5 Jan 2001 15:49:52 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 8A8126A90D; Sat, 6 Jan 2001 10:19:51 +1030 (CST) Date: Sat, 6 Jan 2001 10:19:51 +1030 From: Greg Lehey To: Brad Knowles Cc: Tor.Egge@fast.no, andy.depetter@ops.skynet.be, freebsd-stable@FreeBSD.ORG Subject: Re: Problems with corrupted vinum devices... Message-ID: <20010106101951.A48589@wantadilla.lemis.com> References: <200101051644.RAA17887@midten.fast.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from blk@skynet.be on Fri, Jan 05, 2001 at 06:25:29PM +0100 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 5 January 2001 at 18:25:29 +0100, Brad Knowles wrote: > At 5:44 PM +0100 2001/1/5, Tor.Egge@fast.no wrote: > >> I suggest increasing INITIAL_DRIVES in vinumvar.h to avoid array >> resize and the associated race conditions. When I tried to configure >> vinum to use 14 disks yesterday, the machine immediately crashed with >> a trap 12 in response to 'vinum create'. I bumped INITIAL_DRIVES to >> 16 to avoid the drive array resize that caused the problem. I bumped >> INITIAL_SUBDISKS_IN_PLEX too, just to be safe. > > IIRC, there is a hard limit of 32 physical disks that you can > define, but I've only defined eight. I've removed that limit in -CURRENT. >> To avoid similar races with RAID-5 under high load or with >> softupdates, I had to bump INITIAL_LOCKS to avoid a fatal range lock >> array resize. > > We're not using RAID-5, but we are using softupdates. I'll have > to look into the code and see if this patch makes sense for us, and I > may end up doing a "make update" to bring us up to the latest OS > sources, etc... before I try much of anything else. No, the patch addresses a different problem. This is also a configuration problem, so it has nothing to do with soft updates. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message