From owner-freebsd-geom@FreeBSD.ORG Thu Sep 14 16:11:50 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 ECB0116A416 for ; Thu, 14 Sep 2006 16:11:50 +0000 (UTC) (envelope-from peter_giessel@dot.state.ak.us) Received: from jnumail1.state.ak.us (jnumail1.state.ak.us [146.63.81.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07DF443D81 for ; Thu, 14 Sep 2006 16:11:41 +0000 (GMT) (envelope-from peter_giessel@dot.state.ak.us) Received: from smtpj.state.ak.us (localhost [127.0.0.1]) by jnumail1.state.ak.us (iPlanet Messaging Server 5.2 HotFix 2.04 (built Feb 8 2005)) with ESMTP id <0J5L00N8MBNH4P@jnumail1.state.ak.us> for freebsd-geom@freebsd.org; Thu, 14 Sep 2006 08:11:41 -0800 (AKDT) Received: from [192.168.0.193] ([158.145.111.132]) by smtpj.state.ak.us (iPlanet Messaging Server 5.2 HotFix 2.04 (built Feb 8 2005)) with ESMTP id <0J5L00519BNGN0@smtpj.state.ak.us> for freebsd-geom@freebsd.org; Thu, 14 Sep 2006 08:11:40 -0800 (AKDT) Date: Thu, 14 Sep 2006 08:11:39 -0800 From: "Peter A. Giessel" To: freebsd-geom@freebsd.org Message-id: <45097F3B.2060606@dot.state.ak.us> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) Subject: 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: Thu, 14 Sep 2006 16:11:51 -0000 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 I'm using a raid5: --------------------------------- 4 drives: D five State: up /dev/ad10s1 A: 47/190779 MB (0%) D four State: up /dev/ad11s1 A: 47/190779 MB (0%) D three State: up /dev/ad12s1 A: 47/190779 MB (0%) D two State: up /dev/ad14s1 A: 0/190732 MB (0%) D eleven State: up /dev/ad16s1 A: 47/190779 MB (0%) 1 volume: V array State: up Plexes: 1 Size: 745 GB 1 plex: P array.p0 R5 State: degraded Subdisks: 5 Size: 745 GB 6 subdisks: S array.p0.s5 State: up D: eleven Size: 186 GB S array.p0.s4 State: up D: five Size: 186 GB S array.p0.s3 State: up D: four Size: 186 GB S array.p0.s2 State: up D: three Size: 186 GB S array.p0.s1 State: up D: two Size: 186 GB S array.p0.s0 State: down D: one Size: 186 GB --------------------------------- Drive one failed, so we took it out, put a new one in, repartitioned, created the config file "driveone": ----------driveone--------- drive one device /dev/ad18s1h --------------------------- 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. Any advice that you could give would be very much appreciated.