From owner-freebsd-fs@FreeBSD.ORG  Tue Jul 12 17:39:27 2011
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B9BEF106564A
	for <freebsd-fs@freebsd.org>; Tue, 12 Jul 2011 17:39:27 +0000 (UTC)
	(envelope-from fjwcash@gmail.com)
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com
	[209.85.213.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 79CAC8FC13
	for <freebsd-fs@freebsd.org>; Tue, 12 Jul 2011 17:39:27 +0000 (UTC)
Received: by yxl31 with SMTP id 31so1020171yxl.13
	for <freebsd-fs@freebsd.org>; Tue, 12 Jul 2011 10:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=G5naC1Tu4M3zIr90j+AKYoxshD36WChnAjfNt9j0vos=;
	b=Qkx3ssTWTn8c4CooOsvDsXukglkVH2vfD1JuFVMASwSVHJ/UH4SSvAmn8dGpXaiem8
	UWrnbNflmU3oZiAR+h4bXRyD0DIGpMYethvwbg53Ca/6rU07Mm3YaVJOsK3RTObF6Or7
	WwFHq0MaRF/w1OxRNlezAfJcbQL7vWlqkRlHY=
MIME-Version: 1.0
Received: by 10.90.23.39 with SMTP id 39mr364579agw.125.1310492366770; Tue, 12
	Jul 2011 10:39:26 -0700 (PDT)
Received: by 10.90.118.7 with HTTP; Tue, 12 Jul 2011 10:39:26 -0700 (PDT)
In-Reply-To: <CAOjFWZ5phY2o1ERfPeOppgHvn5S4PySuoWtKMesXYGW+RPK2sw@mail.gmail.com>
References: <74BE0A7A690143C2AE50D102D4C850F7@multiplay.co.uk>
	<CAOjFWZ5phY2o1ERfPeOppgHvn5S4PySuoWtKMesXYGW+RPK2sw@mail.gmail.com>
Date: Tue, 12 Jul 2011 10:39:26 -0700
Message-ID: <CAOjFWZ4HzBHAGkkxKLOzYgu4o9x9JuRsquW9R2wiSbj2ffMtxg@mail.gmail.com>
From: Freddie Cash <fjwcash@gmail.com>
To: Steven Hartland <killing@multiplay.co.uk>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: freebsd-fs@freebsd.org
Subject: Re: strange zpool status output
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 17:39:27 -0000

On Tue, Jul 12, 2011 at 10:38 AM, Freddie Cash <fjwcash@gmail.com> wrote:

> On Tue, Jul 12, 2011 at 5:22 AM, Steven Hartland <killing@multiplay.co.uk>wrote:
>
>> zpool status
>>  pool: tank
>> 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://www.sun.com/msg/ZFS-**8000-8A<http://www.sun.com/msg/ZFS-8000-8A>
>> scrub: scrub in progress for 307445734561825859h27m, 6.96% done,
>> 307445734561825849h8m to go
>>
>
> Nothing odd.  It takes a good 15 minutes or so for the scrub code to
> determine just how fast things are going, how much work there is to do, etc
> etc, before the progress line makes sense.  The "time in progress" and "time
> to go" numbers will fluctuate rapidly for the first little while, and then
> settle down into "normal" numbers.
>

And, if there are any writes happening in the pool, or snapshots being
created/deleted, then the numbers will also be wonky as the "end point" is
constantly being moved further into the "future".

-- 
Freddie Cash
fjwcash@gmail.com