From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 23:38:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED0A516A4CE; Sun, 7 Nov 2004 23:38:03 +0000 (GMT) Received: from spxau01.smeglobalnet.net (spxau01.smeglobalnet.net [203.57.65.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 056E043D48; Sun, 7 Nov 2004 23:38:03 +0000 (GMT) (envelope-from andy@bradfieldprichard.com.au) Received: from bpgate.speednet.com.au ([203.41.15.9]) by spxau01.smeglobalnet.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 8 Nov 2004 10:32:53 +1100 Received: from bpgate.speednet.com.au (localhost [127.0.0.1]) iA7NWpPV056559; Mon, 8 Nov 2004 10:32:51 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) Received: from localhost (andy@localhost)iA7NWoFl056556; Mon, 8 Nov 2004 10:32:50 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) X-Authentication-Warning: bpgate.speednet.com.au: andy owned process doing -bs Date: Mon, 8 Nov 2004 10:32:50 +1100 (EST) From: Andy Farkas X-X-Sender: andy@bpgate.speednet.com.au To: Matthias Schuendehuette In-Reply-To: <200411071124.35056.msch@snafu.de> Message-ID: <20041108091558.C55995@bpgate.speednet.com.au> References: <20041107003413.GQ24507@wantadilla.lemis.com> <20041107030748.GZ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-OriginalArrivalTime: 07 Nov 2004 23:32:53.0859 (UTC) FILETIME=[1A929330:01C4C522] cc: Greg 'groggy' Lehey cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 23:38:04 -0000 On Sun, 7 Nov 2004, Matthias Schuendehuette wrote: > 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... :-) I can confirm that 'classic' vinum will panic if loaded before other non- vinum partitions are mounted. (on a 5.3-STABLE SMP box). This is not too encouraging either: > man gvinum No manual entry for gvinum :( Right now I am in the middle of replacing a dead disk in my 'classic' vinum raid5 volume. Thinking that now might be a good time to check out gvinum, I tried this command (despite the above message): # gvinum load unknown command 'load' # ...but geom_vinum loaded anyways! But it got it wrong :( The following, which appeared in /var/log/all.log, should all be the same subdisk name. It looks like gvinum found some old volume info.. I have used both volume names, but now should only be one (holden): Nov 8 09:13:08 hummer kernel: GEOM_VINUM: subdisk hewey.p0.s2 is up Nov 8 09:13:08 hummer kernel: GEOM_VINUM: subdisk hewey.p0.s1 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s7 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s6 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s3 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s2 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s5 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s4 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s0 is up (ps. why is this a 'kern.critical' error?) and now it looks like I can't get rid of gvinum to go back and try 'classic' vinum: # kldstat Id Refs Address Size Name 1 4 0xc0400000 2bd7e0 kernel 2 1 0xc1af1000 2000 green_saver.ko 3 1 0xc1dfa000 10000 geom_vinum.ko # kldunload geom_vinum kldunload: can't unload file: Operation not supported # gvinum unload unknown command 'unload' # Oh well.. reboot, here we come.. -andyf