Date: Fri, 15 Sep 2006 14:56:07 +0200 From: Ulf Lilleengen <lulf@stud.ntnu.no> To: "Peter A. Giessel" <peter_giessel@dot.state.ak.us> Cc: freebsd-geom@freebsd.org Subject: Re: Replacing failed drive in gvinum causes panic Message-ID: <20060915125607.GA2722@stud.ntnu.no> In-Reply-To: <45097F3B.2060606@dot.state.ak.us> References: <45097F3B.2060606@dot.state.ak.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On tor, sep 14, 2006 at 08:11:39 -0800, Peter A. Giessel wrote: > I'm getting the same thing as Ludo was getting about 9 months ago with > both 5.4 and 6.1 > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=55224+0+/usr/local/www/db/text/2005/freebsd-geom/20051225.freebsd-geom *snip* > > now, "gvinum create driveone" results in an immediate panic. Sometimes > gvinum will print: > "array.p0 degraded -> up" just before the panic. > > This seems odd to me since it should take a while for array.p0.s0 to > come back online, so its like its skipping the rebuild, coming up in > an odd state, and immediately panic'ing. Do you also have a different sized drive as Ludo had? The thing is, that a subdisk has a drive_offset that indicates where on the drive that a subdisk begin. Gvinum may not actually handle this. -- Mvh Ulf Lilleengen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060915125607.GA2722>