From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 11:47:27 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A583106566C for ; Mon, 12 Jul 2010 11:47:27 +0000 (UTC) (envelope-from zw_uk@hotmail.com) Received: from bay0-omc4-s12.bay0.hotmail.com (bay0-omc4-s12.bay0.hotmail.com [65.54.190.214]) by mx1.freebsd.org (Postfix) with ESMTP id 15D728FC13 for ; Mon, 12 Jul 2010 11:47:26 +0000 (UTC) Received: from BAY150-W17 ([65.54.190.199]) by bay0-omc4-s12.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 12 Jul 2010 04:35:26 -0700 Message-ID: X-Originating-IP: [81.5.176.176] From: S M To: Date: Mon, 12 Jul 2010 11:35:27 +0000 Importance: Normal In-Reply-To: <40EB15F2-5479-4884-AFE4-3D26BAF2C4A7@gmail.com> References: , <40EB15F2-5479-4884-AFE4-3D26BAF2C4A7@gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 12 Jul 2010 11:35:26.0859 (UTC) FILETIME=[52E365B0:01CB21B6] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: ZFS - Unable to replace replacing drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2010 11:47:27 -0000 > What structure is this supposed to be? A stripe of two three-way mirrors= ? > And you did "zpool replace vault /dev/ad6.eli /dev/da99.eli" ? Hi Ivan and all=2C Yes=2C this was meant to be 2x vdevs which are striped=2C each vdev being a= 3 way mirror.=20 Yes=2C /dev/ad6.eli was a problem drive so I plugged /dev/da99.eli into the= LSI controller and=2C as you said=2C ran zpool replace vault /dev/ad6.eli = /dev/da99.eli. Then that drive failed too (coincidence?) but now I can't ge= t rid of the replacing drives. I've tried all manner of combinations of commands to remove them=2C even tr= ied finding another drive=2C changing device.hints to rename that as da99 (= which then comes up as FAULTED but the same problem as above happens).=20 Stephen - I had a look at dd'ing the drive to get enough zfs metadata out t= o trick zpool into accepting the drive and trying to resilver=2C but the pr= oblem is that the drive is too far gone - when I plug it in=2C it just comp= letely hangs the LSI controller=2C followed by screenfuls of geli errors an= d timeout errors. When I plug it into the motherboard controller=2C it does= n't even detect it properly. I can't even get to a point of being able to r= un seatools against it=2C so that drive is going to get replaced. One thing I've noticed is that the zfs implementation doesn't appear to lik= e using the degraded vdev=3B I thought it tended to favour blank drives to = even everything out but it seems to be using the full vdev where it can - i= s that purely because of the degraded vdev? If so is there anything I can d= o to restore it? I don't have enough drives to back up the pool and remake = it=2C and that's not a permanent fix anyway. Cheers Stu =20 _________________________________________________________________ http://clk.atdmt.com/UKM/go/197222280/direct/01/ Do you have a story that started on Hotmail? Tell us now=