From owner-freebsd-stable Fri Jan 5 15:47:56 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 15:47: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 AD66D37B400 for ; Fri, 5 Jan 2001 15:47:52 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id BBD166A918; Sat, 6 Jan 2001 10:17:50 +1030 (CST) Date: Sat, 6 Jan 2001 10:17:50 +1030 From: Greg Lehey To: Tor.Egge@fast.no Cc: blk@skynet.be, andy.depetter@ops.skynet.be, freebsd-stable@FreeBSD.ORG Subject: Re: Problems with corrupted vinum devices... Message-ID: <20010106101750.Z48589@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: <200101051644.RAA17887@midten.fast.no>; from Tor.Egge@fast.no on Fri, Jan 05, 2001 at 05:44:02PM +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 17:44:02 +0100, Tor.Egge@fast.no wrote: >> However, at some point within the next couple of hours (we're not >> quite sure when), the machine crashed, and vinum failed to come up on >> the reboot. We had to comment out the /etc/fstab entries that >> referred to the vinum volumes, and since then have been trying to >> debug the problems as to why vinum can't find or start any devices at >> all. > > 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. I don't think these issues are related. I'm still trying to figure out what Brad did, but my best guess is some problem with the disk labelling. > 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. > > For 4.2-STABLE, I'm currently using the following patch to implement > the workarounds: Wait for me to test it and I'll commit it. At this stage I don't think there's any great advantage in distributing patches. 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