From owner-freebsd-fs@freebsd.org Sun Nov 20 20:03:37 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F006FC4C9B0 for ; Sun, 20 Nov 2016 20:03:37 +0000 (UTC) (envelope-from marek.salwerowicz@misal.pl) Received: from mail3.misal.pl (mail3.misal.pl [83.19.131.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A2DF21A9E; Sun, 20 Nov 2016 20:03:37 +0000 (UTC) (envelope-from marek.salwerowicz@misal.pl) Received: from localhost (mail3.misal.pl [127.0.0.1]) by mail3.misal.pl (Postfix) with ESMTP id 12597317C; Sun, 20 Nov 2016 21:03:33 +0100 (CET) X-Virus-Scanned: amavisd X-Spam-Flag: NO X-Spam-Score: -3 X-Spam-Level: X-Spam-Status: No, score=-3 tagged_above=-9999 required=9 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: mail3.misal.pl (amavisd-new); dkim=pass (1024-bit key) header.d=misal.pl Received: from mail3.misal.pl ([127.0.0.1]) by localhost (mail3.misal.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id UxXLae3va_XE; Sun, 20 Nov 2016 21:03:32 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.10.3 mail3.misal.pl B42803175 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=misal.pl; s=misal.pl; t=1479672211; bh=qgIPbrsVpIi77bSlgOjKARj8eaZFyyNsfh+h5sZXW1w=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=spFhw2wdPMtz7RcLVCUS3iQKhFNbpYnZlrKojCTeKXrxIjmaljc1q66RyhGLQ4d2N lsA3eqGaD3OWV8zUdGNs4YcZXK9g/+i9FzZ/SDztNOsBz7kN2STAIn8JtvITNSFT2E wx4FcSfDBsQ+9BbdG8YF5+s0UuZ+9ophG80JdftA= Subject: Re: zpool raidz2 stopped working after failure of one drive To: Gary Palmer References: <20161120150235.GB99344@in-addr.com> Cc: "freebsd-fs@freebsd.org" From: Marek Salwerowicz Message-ID: Date: Sun, 20 Nov 2016 21:03:30 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161120150235.GB99344@in-addr.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 20:03:38 -0000 W dniu 2016-11-20 o 16:02, Gary Palmer pisze: > >> However, I am concerned by the fact that one drive's failure has blocked >> completely zpool. >> Is it normal normal behaviour for zpools ? > > What is the setting in > > zpool get failmode > > By default it is "wait", which I suspect is what caused your issues. > See the man page for zpool for more. Indeed, it's wait. However, I was trying to reproduce the problem in a VM by removing SATA disk on the fly from raidz2 (while pool was under I/O by bonnie++ ), and it worked correctly - drive state is "REMOVED" in "zpool status" command. But the pool works correctly. Taking into account this PR, I am wondering if it might be a hardware issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348 > zfsd in 11.0 and later is the current path to hot spare management > in FreeBSD. FreeBSD 10.x does not have the ability to automatically use > hot spares to replace failing drives. Thanks - I will try it out. Cheers Marek -- Marek Salwerowicz MISAL-SYSTEM tel. + 48 222 198891