Date: Sat, 12 Aug 2000 10:51:57 +0930 From: Greg Lehey <grog@lemis.com> To: Joe Modjeski <jmodjeski@ms1.northlink.com> Cc: freebsd-scsi@freebsd.org Subject: Re: to Vinum or not to Vinum Message-ID: <20000812105156.E69211@wantadilla.lemis.com> In-Reply-To: <00101B7A7FDDD311A89500A0CC56C79048B8@MS1>; from jmodjeski@ms1.northlink.com on Fri, Aug 11, 2000 at 05:40:26PM -0700 References: <00101B7A7FDDD311A89500A0CC56C79048B8@MS1>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 11 August 2000 at 17:40:26 -0700, Joe Modjeski wrote: > > FreeBSD 4.0-RELEASE #0 > > The default vinum version that came with 4.0. > > no source changes. I use a minimal install and then map the /usr /var /tmp > directories to the Vinum drive once setup. Then extract the kernel source > and install ports to the Raid5 volume > > vinum list: > 5 drives: > D Raid51 State: up Device /dev/da1s1e Avail: > 0/8675 MB (0%) Please don't wrap these lines. > D Raid52 State: up Device /dev/da2s1e Avail: > 0/8675 MB (0%) > D Raid53 State: up Device /dev/da3s1e Avail: > 0/8675 MB (0%) > D Raid54 State: up Device /dev/da4s1e Avail: > 0/8675 MB (0%) > D Raid55 State: up Device /dev/da5s1e Avail: > 0/8675 MB (0%) > > 1 volumes: > V Raid5 State: up Plexes: 1 Size: 33 GB > > 1 plexes: > P Raid5.p0 R5 State: up Subdisks: 5 Size: 33 GB > > 5 subdisks: > S Raid5.p0.s0 State: up PO: 0 B Size: 8675 MB > S Raid5.p0.s1 State: up PO: 512 kB Size: 8675 MB > S Raid5.p0.s2 State: up PO: 1024 kB Size: 8675 MB > S Raid5.p0.s3 State: up PO: 1536 kB Size: 8675 MB > S Raid5.p0.s4 State: up PO: 2048 kB Size: 8675 MB > > I am working on getting the dumps but it is not as easy as it sounds in the > handbook or the link. Don't bother, upgrade to 4-STABLE or 4.1-RELEASE. > I would like to try the version of vinum that was stated to be patched on > the vinum page: > > 28 September 1999: We have seen hangs when perform heavy I/O to RAID-5 > plexes. The symptoms are that processes hang waiting on vrlock and flswai. > Use ps lax to display this information. > Technical explanation: A deadlock arose between code locking stripes on a > RAID-5 plex (vrlock) and code waiting for buffers to be freed (flswai). > > Status: Fix committed to FreeBSD-CURRENT on 5 January 2000. We're waiting to > be reasonably sure that the problem doesn't reoccur, then it will be > committed to -STABLE. > > Actually after looking at the bug report again. I am sure find locks in a > state (vrlock) - using ps axl - noticed this while trying to create the > crash dump today. Hmm. Yes, it's possible that remnants of this bug were still in 4.0. 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-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000812105156.E69211>