From owner-freebsd-fs@FreeBSD.ORG  Wed Sep  3 21:27:14 2003
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 649EF16A4E0
	for <freebsd-fs@freebsd.org>; Wed,  3 Sep 2003 21:27:14 -0700 (PDT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9E12A43FE5
	for <freebsd-fs@freebsd.org>; Wed,  3 Sep 2003 21:27:13 -0700 (PDT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 9074D72DA4; Wed,  3 Sep 2003 21:27:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id 8DBCA72DA3; Wed,  3 Sep 2003 21:27:13 -0700 (PDT)
Date: Wed, 3 Sep 2003 21:27:13 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr>
In-Reply-To: <wpwucpsgf9.fsf@heho.snv.jussieu.fr>
Message-ID: <20030903212556.C88884@carver.gumbysoft.com>
References: <wpwucpsgf9.fsf@heho.snv.jussieu.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-fs@freebsd.org
Subject: Re: very slow fsck on bad disk
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
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: Thu, 04 Sep 2003 04:27:14 -0000

On Wed, 3 Sep 2003, Arno J. Klaassen wrote:

>     fsck_ffs -y -b 32 /dev/ad2s1e
>
> I started this .... "last saturday" and it's still running.
> When I look at the dmesg or /var/log messages, my eye
> got triggered by this :
>
>
>   Sep  3 23:02:27 tabarnac kernel: ad2: hard error cmd=read fsbn 16405947 status=59 error=40
>   Sep  3 23:02:32 tabarnac kernel: ad2: hard error cmd=read fsbn 16405948 status=59 error=40

[... disk errors ...]

> Am i wrong or does this smell like "each surface error is queued
> for syslog, syslog print is triggered every 5 seconds, progress
> on fsck ata-disks is hold until next syslog message is printed"

It isn't trying to log to the defective volume, is it? And the delays are
probably the disk resetting.  Errors and timeouts take a while.

I would say you are the proud owner of a new doorstop. :)

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org