From owner-freebsd-geom@FreeBSD.ORG Fri Sep 15 12:56:10 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F74716A47B for ; Fri, 15 Sep 2006 12:56:10 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from signal.itea.ntnu.no (signal.itea.ntnu.no [129.241.190.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7AB843D49 for ; Fri, 15 Sep 2006 12:56:09 +0000 (GMT) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by signal.itea.ntnu.no (Postfix) with ESMTP id 49BBC34282; Fri, 15 Sep 2006 14:56:06 +0200 (CEST) Received: from gaupe.stud.ntnu.no (gaupe.stud.ntnu.no [129.241.56.184]) by signal.itea.ntnu.no (Postfix) with ESMTP; Fri, 15 Sep 2006 14:56:04 +0200 (CEST) Received: by gaupe.stud.ntnu.no (Postfix, from userid 2312) id DDF1FD0009; Fri, 15 Sep 2006 14:56:07 +0200 (CEST) Date: Fri, 15 Sep 2006 14:56:07 +0200 From: Ulf Lilleengen To: "Peter A. Giessel" Message-ID: <20060915125607.GA2722@stud.ntnu.no> References: <45097F3B.2060606@dot.state.ak.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45097F3B.2060606@dot.state.ak.us> User-Agent: Mutt/1.5.9i X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Cc: freebsd-geom@freebsd.org Subject: Re: Replacing failed drive in gvinum causes panic X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 12:56:10 -0000 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