From owner-freebsd-fs@FreeBSD.ORG Tue Oct 30 16:32:14 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 23075425 for ; Tue, 30 Oct 2012 16:32:14 +0000 (UTC) (envelope-from paul-freebsd@fletchermoorland.co.uk) Received: from hercules.mthelicon.com (hercules.mthelicon.com [66.90.118.40]) by mx1.freebsd.org (Postfix) with ESMTP id DAA038FC14 for ; Tue, 30 Oct 2012 16:32:12 +0000 (UTC) Received: from demophon.fletchermoorland.co.uk (hydra.fletchermoorland.co.uk [78.33.209.59] (may be forged)) (authenticated bits=0) by hercules.mthelicon.com (8.14.5/8.14.5) with ESMTP id q9UGWAYj093196; Tue, 30 Oct 2012 16:32:11 GMT (envelope-from paul-freebsd@fletchermoorland.co.uk) Message-ID: <5090010A.4050109@fletchermoorland.co.uk> Date: Tue, 30 Oct 2012 16:32:10 +0000 From: Paul Wootton User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120530 Thunderbird/12.0.1 MIME-Version: 1.0 To: Ronald Klop Subject: Re: ZFS RaidZ-2 problems References: <508F98F9.3040604@fletchermoorland.co.uk> <1351598684.88435.19.camel@btw.pki2.com> <508FE643.4090107@fletchermoorland.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2012 16:32:14 -0000 On 10/30/12 16:10, Ronald Klop wrote: > On Tue, 30 Oct 2012 15:37:55 +0100, Paul Wootton > wrote: > >> On 10/30/12 12:04, Dennis Glatting wrote: >>> I've had this problem too. Here is what I can tell you for my case. >>> ... I replaced the card, the cable, and the disks themselves leaving >>> only one other possibility -- the power supply. The faulting array >>> was on a separate cable from the power supply. I replaced the power >>> supply, going from a 1,000W to 1,300W, and the power cables to the >>> disks. Not a problem since. >> >> While I can accept that I might have a bad power supply. or cables, >> my main concern is that I have only 1 drive showing as "Unavail" on a >> RAIDZ-2 and the pack is showing "Faulted". >> I would have expected that pack to continue working with 2 bad >> drives, and would have failed if I had 3rd one fail >> >> Paul > > Isn't your problem something else than a non-working pool with one > broken disk. I guess it still worked before you exported it. Your > actual problem is 'zpool import' does not work for your pool. Maybe > there is more broken than one disk. > > Why did you export/import to fix anything in stead of replacing the > faulted disk? > > (I'm not into the code details of ZFS, so can't help you with > everything.) > > Ronald. > > The pool was marked as faulted before I tried exporting/importing.ZFS should have marked the pool as degraded, so I wondered if I exported and then reimported the pool, ZFS would taste each of the disks and imported the pool in a degraded mode.