From owner-freebsd-fs@FreeBSD.ORG Thu Jun 10 09:41:17 2010 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 353B9106566B for ; Thu, 10 Jun 2010 09:41:17 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id EBCFA8FC13 for ; Thu, 10 Jun 2010 09:41:16 +0000 (UTC) Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta02.westchester.pa.mail.comcast.net with comcast id U9Na1e0050vyq2s529U1M7; Thu, 10 Jun 2010 09:28:01 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta05.westchester.pa.mail.comcast.net with comcast id U9Tz1e0053S48mS3R9U0h2; Thu, 10 Jun 2010 09:28:01 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 6C8BA9B418; Thu, 10 Jun 2010 02:27:58 -0700 (PDT) Date: Thu, 10 Jun 2010 02:27:58 -0700 From: Jeremy Chadwick To: Alexander Leidinger Message-ID: <20100610092758.GA67752@icarus.home.lan> References: <20100609162627.11355zjzwnf7nj8k@webmail.leidinger.net> <20100609144355.GL72453@cicely7.cicely.de> <20100610112345.644960lrau3mxfk0@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100610112345.644960lrau3mxfk0@webmail.leidinger.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: ticso@cicely.de, fs@FreeBSD.org Subject: Re: Do we want a periodic script for a zfs scrub? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2010 09:41:17 -0000 On Thu, Jun 10, 2010 at 11:23:45AM +0200, Alexander Leidinger wrote: > But I'm a little bit surprised, when I scrub a pool of 3 times 250 > GB disks in RAIDZ configuration, it is finished fast (a fraction of > a day... maybe an hour or two). Initially it displays a very long > time (>400 hours), but this is reducing after a while drastically. For what it's worth, Solaris does the exact same thing (initially shows a very long duration, which keeps getting longer, but then reduces after some time and begins catching up quickly). It didn't originally behave this way (on FreeBSD or Solaris) so there's probably a justified reason for it. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |