From owner-freebsd-fs@FreeBSD.ORG  Tue Mar  3 23:00:30 2009
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 3851310657C3;
	Tue,  3 Mar 2009 23:00:30 +0000 (UTC)
	(envelope-from stef-list@memberwebs.com)
Received: from mx.npubs.com (mail.wsfamily.com [209.66.100.224])
	by mx1.freebsd.org (Postfix) with ESMTP id 2116B8FC0A;
	Tue,  3 Mar 2009 23:00:29 +0000 (UTC)
	(envelope-from stef-list@memberwebs.com)
Received: from mx.npubs.com (avhost [209.66.100.194])
	by mx.npubs.com (Postfix) with ESMTP id A603AEFB8E6;
	Tue,  3 Mar 2009 22:38:11 +0000 (UTC)
Received: from northstar-srv2 (unknown [172.27.2.11])
	by mx.npubs.com (Postfix) with ESMTP id 8E51DEFB6DA;
	Tue,  3 Mar 2009 22:38:10 +0000 (UTC)
From: Stef <stef-list@memberwebs.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Paul Wootton <paul@fletchermoorland.co.uk>
References: <E1LeFx9-0000LA-00.c-h-mail-ru@f86.mail.ru>
	<200903030941.41226.paul@fletchermoorland.co.uk>
Content-Type: text/plain; charset=windows-1251
Content-Transfer-Encoding: 7bit
Message-Id: <20090303223810.8E51DEFB6DA@mx.npubs.com>
X-Virus-Scanned: ClamAV using ClamSMTP
Date: Tue,  3 Mar 2009 22:38:11 +0000 (UTC)
Cc: freebsd-fs@freebsd.org, Cache <c-h@mail.ru>, freebsd-current@freebsd.org
Subject: Re: Help! zpool corrupted!
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stef@memberwebs.com
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, 03 Mar 2009 23:00:30 -0000

Paul Wootton wrote:
> If the SMART data from the drive does not show bad then I would probably agree 
> that the drive ok.

I've seen many drives with unreadable blocks, that don't show any
problems in the SMART error logs. The SMART statistics on those drives
are slightly different, but nothing that distinguishes it from an okay
drive that has remapped a few sectors.

I think that FreeBSD's timeouts are usually much higher than that of
many 'desktop' drives. The drive will keep trying to read the sector
long after FreeBSD has given up. Eventually the drive semi-succeeds and
then doesn't consider it a failure. Ergo no SMART error log.

Cheers,

Stef