From owner-freebsd-stable@freebsd.org Sun Sep 18 13:09:21 2016 Return-Path: Delivered-To: freebsd-stable@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 C1E06BDECB0 for ; Sun, 18 Sep 2016 13:09:21 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 600201108 for ; Sun, 18 Sep 2016 13:09:21 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: by mail-wm0-x243.google.com with SMTP id l132so9608719wmf.1 for ; Sun, 18 Sep 2016 06:09:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=from:date:to:subject:message-id:mime-version :content-transfer-encoding; bh=I9SbEv8bJI3Wzp4S5PhEKY2AZZiobTt4W/xjx/SO67U=; b=ovc7j1Og6yw3U/qvc6pWxL8AIMlam5o8NgOIuZqGYoGpWkZImVyBOgQ3cOReDMwuk1 aiynHWzOEyQBELiBBkzWvTc42US6V/wrw8jwfObG4MnOqbUkby71pGGX8+feX0tLVoxJ hQtK4z24ua6D3Yk02Unj0R3vCZvFTw5WPc/w3k44+wWlMC4irf8wB/t+mn5tSM/ebMWi anqTcpp9RTXIwEspXqTHdiIpmzG4+oFw1QtcGqzEg+6OIFEsv5VR9V/AjlmIyUh+4st7 4FR4JH7s26kdQr5YgAETeaiHTC2xoRTM47Zs7ElngSX94K6zujYQtA6c6aJPulDxJX35 MPCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:subject:message-id:mime-version :content-transfer-encoding; bh=I9SbEv8bJI3Wzp4S5PhEKY2AZZiobTt4W/xjx/SO67U=; b=Bf4I4gzeIrP4m7k+XzUZ2IAUBQvWCazJ/WbjY/2AcX1jisQTkGghLk3R8boHMYDwQv kWkUWCcW1Rt3aFQ3XZnRrfIJbZo3ICC+7KbQn8t1b/l/n/cA/0Gbz+waJ6Uk7ASL4/I9 FXNgAh2A/Gyyr+DO5Vyhgb8npz/gEJdM2i7vDHeai2+fn0vDuDZ+S+R/45TrUT8jC44U 1Vzjfbejbh4f41ZXdtGSSuUFLvA0bCtkJtbLtO8USu1DhCVs9olauZ3LP9cMWy3b+14B X7F3bNy0rGrqZqj7Q1lHPwEZXyZKkMyd04noxphtPahKYfVTmrADiDNbZo7jXIV2AOqF Tqlg== X-Gm-Message-State: AE9vXwMpNhQUHzZxHBuJMh7a6wDkUgvh2xMEfN6As1+GqccAEoA08tvHfOJ8nogC7FWP3A== X-Received: by 10.194.109.229 with SMTP id hv5mr22264895wjb.131.1474204159599; Sun, 18 Sep 2016 06:09:19 -0700 (PDT) Received: from ubm.strangled.net (ipb21a85d1.dynamic.kabel-deutschland.de. [178.26.133.209]) by smtp.gmail.com with ESMTPSA id lj2sm17815660wjc.38.2016.09.18.06.09.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Sep 2016 06:09:19 -0700 (PDT) From: Marc UBM Bocklet X-Google-Original-From: Marc "UBM" Bocklet Date: Sun, 18 Sep 2016 15:09:17 +0200 To: freebsd-stable Subject: zfs resilver keeps restarting Message-Id: <20160918150917.09f9448464d84d4e50808707@gmail.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 13:09:21 -0000 Hi all, due to two bad cables, I had two drives drop from my striped raidz2 pool (built on top of geli encrypted drives). I replaced one of the drives before I realized that the cabling was at fault - that's the drive which is being replaced in the ouput of zpool status below. I have just installed the new cables and all sata errors are gone. However, the resilver of the pool keeps restarting. I see no errors in /var/log/messages, but zpool history -i says: 2016-09-18.14:56:21 [txg:1219501] scan setup func=2 mintxg=3 maxtxg=1219391 2016-09-18.14:56:51 [txg:1219505] scan done complete=0 2016-09-18.14:56:51 [txg:1219505] scan setup func=2 mintxg=3 maxtxg=1219391 2016-09-18.14:57:20 [txg:1219509] scan done complete=0 2016-09-18.14:57:20 [txg:1219509] scan setup func=2 mintxg=3 maxtxg=1219391 2016-09-18.14:57:49 [txg:1219513] scan done complete=0 2016-09-18.14:57:49 [txg:1219513] scan setup func=2 mintxg=3 maxtxg=1219391 2016-09-18.14:58:19 [txg:1219517] scan done complete=0 2016-09-18.14:58:19 [txg:1219517] scan setup func=2 mintxg=3 maxtxg=1219391 2016-09-18.14:58:45 [txg:1219521] scan done complete=0 2016-09-18.14:58:45 [txg:1219521] scan setup func=2 mintxg=3 maxtxg=1219391 I assume that "scan done complete=0" means that the resilver didn't finish? pool layout is the following: pool: pool state: DEGRADED 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 Sun Sep 18 14:51:39 2016 235G scanned out of 9.81T at 830M/s, 3h21m to go 13.2M resilvered, 2.34% done config: NAME STATE READ WRITE CKSUM pool DEGRADED 0 0 0 raidz2-0 ONLINE 0 0 0 da6.eli ONLINE 0 0 0 da7.eli ONLINE 0 0 0 ada1.eli ONLINE 0 0 0 ada2.eli ONLINE 0 0 0 da10.eli ONLINE 0 0 2 da11.eli ONLINE 0 0 0 da12.eli ONLINE 0 0 0 da13.eli ONLINE 0 0 0 raidz2-1 DEGRADED 0 0 0 da0.eli ONLINE 0 0 0 da1.eli ONLINE 0 0 0 da2.eli ONLINE 0 0 1 (resilvering) replacing-3 DEGRADED 0 0 1 10699825708166646100 UNAVAIL 0 0 0 was /dev/da3.eli da4.eli ONLINE 0 0 0 (resilvering) da3.eli ONLINE 0 0 0 da5.eli ONLINE 0 0 0 da8.eli ONLINE 0 0 0 da9.eli ONLINE 0 0 0 errors: No known data errors system is FreeBSD xxx 10.1-BETA1 FreeBSD 10.1-BETA1 #27 r271633: Mon Sep 15 22:34:05 CEST 2014 root@xxx:/usr/obj/usr/src/sys/xxx amd64 controller is SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] Drives are connected via four four-port sata cables. Should I upgrade to 10.3-release or did I make some sort of configuration error / overlook something? Thanks in advance! Cheers, Marc