From owner-freebsd-fs@freebsd.org Fri Oct 30 11:46:37 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 91352A20EED for ; Fri, 30 Oct 2015 11:46:37 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 216E11AE9 for ; Fri, 30 Oct 2015 11:46:37 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wmeg8 with SMTP id g8so9900325wme.1 for ; Fri, 30 Oct 2015 04:46:35 -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=+LPDwiZ6EMZK7qeXDH6/7YHInsuVZaSu3AP7fbacmZg=; b=ZnxHcwLnyCTwy8JLQFdRnEl4oMpZX/IBSHeyzTHN8fjwdL19mdDBi+J4VuDSL5FhFS yVKYkZG60pPC4k4s+9q6fFjvsj9dsr5Hjru7nVGa9qdlF3jyvKoUyK2rK5hZd9a5dEVK 2Vj0LRsxYCraJqungoCzF3Z3lHD3G56A33oMVioTPLs5h/ZqYTC8Xc56C9wPNZNwP51I 8B6aWurIAWnv415gVTBFdA88cTRvLHlCv+sGUXk18TfIDNKpB+IhAE+E3RRrJw40WybN LSH/2LtvjcyeNuwctw958VRYG2d/a1IGXFSkUzr6hn7K2ZqHnVZjU8hNXNcSG9d5/49E 6T6g== 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=+LPDwiZ6EMZK7qeXDH6/7YHInsuVZaSu3AP7fbacmZg=; b=Xl9jeeUZDF9r4ZjkJOfL58dKgbJQjsQLnuuZo/UbuIY+YNv5qqXbl7loh9ysdkmWWH +PnNqWoz5eZRHXdWxoB0DjClcj59Px4GJG1UF17UaPWvOorOAsyLQNGlQQZ8Gse/HkZH nd/v2VphiBRd4mnHFv0skeDHfG5/+8a1DFVXlGRsmxI7ThPMUUfMdn6cGmRnXPq1nyrF 3cVIxgMkEP3szJa63TBI7+paTCP8QWfXv1rTKaftkQ5Wdn16Q2rpEagulYETbnhWmBe5 Y9/NiPK8P6IyNFV7UhXE2XVG+zD9w3jzl3ghbcaG1r4bG6yvMDRSlJjRa+CsZ+4g5keb r//Q== X-Gm-Message-State: ALoCoQlvbT02KORTq30+eMf+8mxXXpzEfARH63M3dYoMnPqdSecfI3rbXR8/RRkj3RrJRZTxKEoK X-Received: by 10.28.211.70 with SMTP id k67mr2761833wmg.38.1446205595324; Fri, 30 Oct 2015 04:46:35 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id 186sm2512994wmp.10.2015.10.30.04.46.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Oct 2015 04:46:34 -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: <563358A3.3030209@multiplay.co.uk> Date: Fri, 30 Oct 2015 11:46:43 +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:46:37 -0000 Ignore my last post just noticed you 9.1 at the end, which is very old, so it could well be this is already fixed; only way to confirm is upgrade an check ;-) Regards Steve 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. >