Date: Mon, 8 Nov 2004 10:32:50 +1100 (EST) From: Andy Farkas <andy@bradfieldprichard.com.au> To: Matthias Schuendehuette <msch@snafu.de> Cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? Message-ID: <20041108091558.C55995@bpgate.speednet.com.au> In-Reply-To: <200411071124.35056.msch@snafu.de> References: <20041107003413.GQ24507@wantadilla.lemis.com> <20041107030748.GZ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <kern.crit> hummer kernel: GEOM_VINUM: subdisk hewey.p0.s2 is up Nov 8 09:13:08 <kern.crit> hummer kernel: GEOM_VINUM: subdisk hewey.p0.s1 is up Nov 8 09:13:09 <kern.crit> hummer kernel: GEOM_VINUM: subdisk holden.p0.s7 is up Nov 8 09:13:09 <kern.crit> hummer kernel: GEOM_VINUM: subdisk holden.p0.s6 is up Nov 8 09:13:09 <kern.crit> hummer kernel: GEOM_VINUM: subdisk holden.p0.s3 is up Nov 8 09:13:09 <kern.crit> hummer kernel: GEOM_VINUM: subdisk holden.p0.s2 is up Nov 8 09:13:09 <kern.crit> hummer kernel: GEOM_VINUM: subdisk holden.p0.s5 is up Nov 8 09:13:09 <kern.crit> hummer kernel: GEOM_VINUM: subdisk holden.p0.s4 is up Nov 8 09:13:09 <kern.crit> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041108091558.C55995>