Date: Sat, 6 Jan 2001 10:19:51 +1030 From: Greg Lehey <grog@lemis.com> To: Brad Knowles <blk@skynet.be> 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> In-Reply-To: <v04220810b67bb339fd40@[172.17.1.121]>; from blk@skynet.be on Fri, Jan 05, 2001 at 06:25:29PM %2B0100 References: <v0422080ab67b97176227@[172.17.1.121]> <200101051644.RAA17887@midten.fast.no> <v04220810b67bb339fd40@[172.17.1.121]>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010106101951.A48589>