Date: Sun, 7 Nov 2004 11:24:34 +0100 From: Matthias Schuendehuette <msch@snafu.de> To: "Greg 'groggy' Lehey" <grog@freebsd.org> Cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? Message-ID: <200411071124.35056.msch@snafu.de> In-Reply-To: <20041107030748.GZ24507@wantadilla.lemis.com> References: <20041107003413.GQ24507@wantadilla.lemis.com> <Pine.LNX.4.44.0411062040240.13098-100000@pancho> <20041107030748.GZ24507@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Sonntag, 7. November 2004 04:07 schrieb Greg 'groggy' Lehey: > On Saturday, 6 November 2004 at 20:40:44 -0600, Mark Linimon wrote: > > On Sun, 7 Nov 2004, Greg 'groggy' Lehey wrote: > >> I can appreciate that the leadup to 5.3-RELEASE has been painful, > >> but what's the purpose of a release which doesn't work? For a > >> large number of Vinum users, 5.3 will be a release to avoid. > > > > Perhaps this deserves an errata entry? > > No, I was mistaken. See my subsequent apology. To clarify the things out of my point of view: gvinum on 5.3-RELEASE seems to work fine as a LVM (LogicalVolumeManager) and for striping (RAID-0) and mirroring (RAID-1). It does *not* work for *writing* on RAID5-volumes in UP (SingleProcessor) environments due to a bug which was fixed too late for 5.3-RELEASE. I'm not aware of any statistics about the use of (g)vinum - but for users of (g)vinum RAID5-Volumes in UP-environments 5.3-RELEASE *is* problematic. Greg remains right here IMHO. RAID5 under 5.3-RELEASE (UP) only works with 'classic' vinum if loaded *after* the system has come up. Perhaps this posting could be a template for the ERRATA entry... :-) -- Ciao/BSD - Matthias Matthias Schuendehuette <msch [at] snafu.de>, Berlin (Germany) PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200411071124.35056.msch>