From owner-freebsd-fs@freebsd.org Fri Oct 30 11:45:15 2015 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 E6A8EA20E62 for ; Fri, 30 Oct 2015 11:45:15 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 888D51A45 for ; Fri, 30 Oct 2015 11:45:15 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wicll6 with SMTP id ll6so8808802wic.1 for ; Fri, 30 Oct 2015 04:45:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay_co_uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=vCVPGOhIl8qgELu/bEN49Ps4f9Y3nwYdaQj7DP1Jyag=; b=kweNKyBGAskKExqtnaRGn/BiaW9jrMSsPxX1wpRUFgT9OT07Mokd6RXU/W2ljJHagC pqrDYBGTVGvtBElOR40RG08N3XVDT5ViKKhhuzfr/q/eYucMUMzEnixA7HsPA1fIMgWR cFLSO7PoVNOLWwo93cE5gFCAE1lM1TLE79k/sVvORdrYfi+D923B7Cvwoy3vJnMg7Z9r r04ZNwxE8QnqHiYZgokAMxq4GgCuKuwMW6/g/JtE21/wCmAE6U3E8d+ytLdA1Xrbh/yJ vEajL+W5GSOMX60zxPix8MLS5JxXPBX/WAlLNMXdCqvohY0YIdwUJ4ekcXdpflILId+J sOZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=vCVPGOhIl8qgELu/bEN49Ps4f9Y3nwYdaQj7DP1Jyag=; b=CuwX4XBf3BgZTb9N9r5Zge9mebD2xYajD88Am0uiOzhPjKH8tD4rqsOfIhOkwhXGhz NF/kh+fmAk3mEvpOKoONVOPhOm+MHLaNn+sgfRe0qieobAYXO2FtedB4h++uuuDdMoCo 02i9BRevklhHBwZW1VgrbalrPv535NHd46p8vbDqYtHD25fZts9e+o21W2pVvkzhjo5I nITSqioZPGCv3GgKReDd5sBX1s+YYv7o5IWFYIoccDfqbvPX/yjTWRHoXIpuATsLHkI1 Ra4qOC2o4sDG95A9wzLLrx2vyfWYMX3za0ypfl/bj9hxvp3ZJLtdlFuTOQRA+kSVEDIT Awnw== X-Gm-Message-State: ALoCoQm1qS+qdZoD+aaoywGDkjsP5S7ET5UaA2br7CSEYtIp+O4fygx2emEFKPlQow9WIVcLfipS X-Received: by 10.194.58.142 with SMTP id r14mr9446092wjq.37.1446205513896; Fri, 30 Oct 2015 04:45:13 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id 77sm2496462wml.20.2015.10.30.04.45.12 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Oct 2015 04:45:12 -0700 (PDT) Subject: Re: ZFS resilver from disk with bad sectors constantly restarts To: freebsd-fs@freebsd.org References: <20151030103614.GL57666@hades.panopticon> From: Steven Hartland Message-ID: <56335851.5070802@multiplay.co.uk> Date: Fri, 30 Oct 2015 11:45:21 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151030103614.GL57666@hades.panopticon> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2015 11:45:16 -0000 What version? On 30/10/2015 10:36, Dmitry Marakasov wrote: > Hi! > > I've just got a case where resilvering a new replacement disk in raidz2 > never finished. > > The problem: one disk in raidz is failing by having a large number of > unreadable sectors. It's replaced with a spare. Resilver though is > constantly restarted with log full of read error from bad disk. > > It looks like this: > > --- > pool: spool > state: ONLINE > status: One or more devices is currently being resilvered. The pool will > continue to function, possibly in a degraded state. > action: Wait for the resilver to complete. > scan: resilver in progress since Wed Oct 28 05:26:28 2015 > 369G scanned out of 9,87T at 123M/s, 22h29m to go > 41,4G resilvered, 3,65% done > config: > > NAME STATE READ WRITE CKSUM > spool ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > ada0 ONLINE 0 0 0 > ada1 ONLINE 0 0 0 > spare-2 ONLINE 0 0 733 > ada11 ONLINE 0 0 0 > ada2 ONLINE 0 0 0 (resilvering) > raidz1-1 ONLINE 0 0 0 > ada3 ONLINE 0 0 0 > ada4 ONLINE 0 0 0 > ada5 ONLINE 0 0 0 > raidz1-2 ONLINE 0 0 0 > ada6 ONLINE 0 0 0 > ada7 ONLINE 0 0 0 > ada10 ONLINE 0 0 0 > spares > 588540573008830286 INUSE was /dev/ada2 > > errors: No known data errors > --- > > `resilver in progress since' date is constantly reset, so resilved > progress cannot pass beyond 5% or so. My guess is that it happens on > read errors on ada11. I think I've seen (resilvering) on ada11 line > couple of times. > > In the end I've had to offline ada11 and after that resilver completed > in under 16 hours. However the situation doesn't seem normal, as I'd > prefer to not lose redundancy with offlining dying disk and still be > able to use it for resilvering (imagine there were bad sectors on ada0/1 > as well, but not intersecting with bad sectors on ada11), or at least > some more verbose indication of why the resilver is constantly restarted. > > I should also note that's outdated FreeBSD 9.1, so maybe that problem > was fixed already. >