From owner-freebsd-fs@FreeBSD.ORG Wed Nov 26 11:04:06 2008 Return-Path: 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 0C2441065672 for ; Wed, 26 Nov 2008 11:04:06 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id B263A8FC12 for ; Wed, 26 Nov 2008 11:04:05 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id E50FD174DE; Wed, 26 Nov 2008 22:04:02 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.20.30.101] (60.218.233.220.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 9AF47171BF; Wed, 26 Nov 2008 22:03:58 +1100 (EST) Message-ID: <492D2D0F.5020300@modulus.org> Date: Wed, 26 Nov 2008 22:03:43 +1100 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Andriy Gapon References: <492D2122.4050203@icyb.net.ua> In-Reply-To: <492D2122.4050203@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: endless zpool 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: Wed, 26 Nov 2008 11:04:06 -0000 Andriy Gapon wrote: > > I noticed that zpool scrub on a certain pool runs "like forever". > I decided to monitor its progress using periodic zpool status command, > once in 10 seconds. > Here's a snippet from the capture around an interesting point. > Please notice two highlighted reports ('oops'). > This is stable/7. Its a bug, and is fixed in 8-current.