From owner-freebsd-fs@FreeBSD.ORG Wed Oct 31 08:23:43 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 D9EE0CAC for ; Wed, 31 Oct 2012 08:23:43 +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 581468FC0C for ; Wed, 31 Oct 2012 08:23:42 +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 1TTTaO-0007lG-41; Wed, 31 Oct 2012 09:23:40 +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 1TTTaN-0003V0-F5; Wed, 31 Oct 2012 09:23:39 +0100 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "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> <5090010A.4050109@fletchermoorland.co.uk> Date: Wed, 31 Oct 2012 09:23:38 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: <5090010A.4050109@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.0 X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_50 autolearn=disabled version=3.2.5 X-Scan-Signature: ba572e8a3bde05b4b19613c12a9e49fc 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: Wed, 31 Oct 2012 08:23:43 -0000 On Tue, 30 Oct 2012 17:32:10 +0100, Paul Wootton wrote: > 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. Weird. I don't know what is happening. I hope somebody else knows it. Ronald.