From owner-freebsd-fs@FreeBSD.ORG Tue Oct 30 16:10:38 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 CA251CF0 for ; Tue, 30 Oct 2012 16:10:38 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id 77BD88FC08 for ; Tue, 30 Oct 2012 16:10:38 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1TTEOg-0003ES-4h; Tue, 30 Oct 2012 17:10:34 +0100 Received: from [81.21.138.17] (helo=ronaldradial.versatec.local) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1TTEOf-0000P8-F3; Tue, 30 Oct 2012 17:10:33 +0100 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Dennis Glatting" , "Paul Wootton" Subject: Re: ZFS RaidZ-2 problems References: <508F98F9.3040604@fletchermoorland.co.uk> <1351598684.88435.19.camel@btw.pki2.com> <508FE643.4090107@fletchermoorland.co.uk> Date: Tue, 30 Oct 2012 17:10:31 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: <508FE643.4090107@fletchermoorland.co.uk> User-Agent: Opera Mail/12.02 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_40 autolearn=disabled version=3.2.5 X-Scan-Signature: a350ae07b5350cdad28cef237d2e7179 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:10:38 -0000 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.