From owner-freebsd-fs@freebsd.org Fri Nov 2 14:17:02 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B5A810F86EB for ; Fri, 2 Nov 2018 14:17:02 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6EBE66D011; Fri, 2 Nov 2018 14:17:01 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: by mail-lj1-x242.google.com with SMTP id g26-v6so1878013lja.10; Fri, 02 Nov 2018 07:17:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dDBPNwSJCZBAdv9vMGOP84Td3YSj1CImZSF/Nz3Y5cs=; b=KkR+om4asSG6swoRKl35H33wxN+PaHIYwbUaDd27yavhwO94FnEZV7ctdnFPdTYcRh qGvpV6go/jp0KPF6Z8LZixf6+itPyL11lG2eWWcdxyexKBz6pb/Rxi/snNDNAzA0YNSd ArY1HmOIu4GdJPMULmJkr4+HhDJdD6qxY5zzUQ/kgrWAVuNm9pTWniKRIck3WrkgBQTM zO2BHCPI0OhfL7mdEMVMuOrSJ220PWKdpo2SjNvAJ/2aH3ncy6XzD6/k27Sxh8evE9zt ZiOnW2WBd+RsGq6UwLjLpaaPoTs0taaI0PRsQ+R0u7sUhIFt5btrFixl5qym6lW6WIuv lVVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dDBPNwSJCZBAdv9vMGOP84Td3YSj1CImZSF/Nz3Y5cs=; b=mdGE27vgQou4AksTb2ouO8jLXyNxBU9m5P5EuEGKYLP25qvHQB2KBauWCO+fC/S+e+ FblbeDKIZx3v/tsO/zWugeiFqF+VL87R4tkbz2ZDsYx7/hIMF6vrvW+usnj7HOpcSmFd pO3edj60PYwkWCHgeg3Y1gFupRdS3eA9SbDgcJKP8a2+VYNpcx/XmjPRrplD/b05GlXC z1g7QxxI3G/ZEbkvDFNVohTkJ8K55kzX598CaTPWv3O453WnVHUFMav33qbSWO0yl4/2 IGeqZyTahZTmoEq+LDRa1R8D62Y4mgzeBGK+8/UHtj++vqB5iQUgayVEGWZWEjC3I9xI wJrQ== X-Gm-Message-State: AGRZ1gI7h9Wsr/IKCrnyCHrrhXpRPEGs479lJl/ji05vQwxwc81HP4uk hr9f4v8KTNp/Jt3nY3zCL6VQqPSLEYDqeLdbNCbTvFFg X-Google-Smtp-Source: AJdET5c2HZRM4h5UpchV2LK6d7qKKYe6Qs7FKS0S/cTY+k49CpcUn5IwGHRpUK26/I3TYl3wVZXGaguF8+8CyfLkdCk= X-Received: by 2002:a2e:920c:: with SMTP id k12-v6mr8398489ljg.178.1541168219322; Fri, 02 Nov 2018 07:16:59 -0700 (PDT) MIME-Version: 1.0 References: <5BDC3DF5.9020501@andyit.com.au> <20181102133254.GA35599@jarvis> In-Reply-To: <20181102133254.GA35599@jarvis> From: Rich Date: Fri, 2 Nov 2018 10:16:51 -0400 Message-ID: Subject: Re: zpool scrub 9TB finishes in ~40 mins To: oshogbo@freebsd.org Cc: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-fs Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2018 14:17:02 -0000 Unless FBSD merged it incompletely, that's very unlikely, b/c zpool status output during resilvers/scrubs changes post-sequential resilver work: from: (void) printf(gettext("\t%s scanned out of %s at %s/s") to: (void) printf(gettext("\t%s scanned at %s/s, "%s issued at %s/s, %s total\n"), So those status messages are older than that work, which is also validated by the version running predating the work merging (r331113 versus r334844). I would _guess_ that it encountered so many metadata errors it couldn't get to a lot of the pool, so it vacuously completed faster. Unless large swathes of the disks were unreadable, that's far more errors than I'd expect from a couple of unreadable blocks each. You and ddrescue might want to be friends, though that might make things worse since the pool has continued being some value of "in use" since the failing disks were last in it. - Rich On Fri, Nov 2, 2018 at 9:36 AM Mariusz Zaborski wrote: > > Probably because: > https://github.com/zfsonlinux/zfs/pull/6256/commits/1c6275b1fcdacd734bb4eefd02a123b6b610ca48 > > FreeBSD commit - r334844. > > > On Fri, Nov 02, 2018 at 02:21:28PM +0100, Miroslav Lachman wrote: > > Andy Farkas wrote on 2018/11/02 13:07: > > > > > # zpool status z > > > pool: z > > > state: ONLINE > > > status: One or more devices has experienced an error resulting in data > > > corruption. Applications may be affected. > > > action: Restore the file in question if possible. Otherwise restore the > > > entire pool from backup. > > > see: http://illumos.org/msg/ZFS-8000-8A > > > scan: scrub in progress since Fri Nov 2 16:59:24 2018 > > > 365G scanned out of 11.9T at 228M/s, 14h47m to go > > > 2.47M repaired, 2.99% done > > > > I definitely need this speed of scrub! 238M/s is awesome. > > I have RAIDZ from 4x ST4000VN000-1H4168 SC43 and the speed of scrub is > > about 20MB/s. > > > > Scrub takes more than week to finish: > > > > pool: tank0 > > state: ONLINE > > status: Some supported features are not enabled on the pool. The pool can > > still be used, but some features are unavailable. > > action: Enable all features using 'zpool upgrade'. Once this is done, > > the pool may no longer be accessible by software that does not > > support > > the features. See zpool-features(7) for details. > > scan: scrub repaired 0 in 262h56m with 0 errors on Sun Sep 16 > > 02:04:25 2018 > > config: > > > > NAME STATE READ WRITE CKSUM > > tank0 ONLINE 0 0 0 > > raidz1-0 ONLINE 0 0 0 > > gpt/disk0tank0 ONLINE 0 0 0 > > gpt/disk1tank0 ONLINE 0 0 0 > > gpt/disk2tank0 ONLINE 0 0 0 > > gpt/disk3tank0 ONLINE 0 0 0 > > > > This is on HP ProLiant ML 110 G5 (very old machine) with only 5GB of RAM. > > > > Miroslav Lachman > > _______________________________________________ > > freebsd-fs@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > -- > Mariusz Zaborski > oshogbo//vx | http://oshogbo.vexillium.org > FreeBSD committer | https://freebsd.org > Software developer | http://wheelsystems.com > If it's not broken, let's fix it till it is!!1