From owner-freebsd-fs@FreeBSD.ORG  Wed Mar 14 14:03:27 2012
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 297CB106564A
	for <freebsd-fs@freebsd.org>; Wed, 14 Mar 2012 14:03:27 +0000 (UTC)
	(envelope-from bfriesen@simple.dallas.tx.us)
Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74])
	by mx1.freebsd.org (Postfix) with ESMTP id E16AA8FC1E
	for <freebsd-fs@freebsd.org>; Wed, 14 Mar 2012 14:03:26 +0000 (UTC)
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	q2EE3JYj013694; Wed, 14 Mar 2012 09:03:20 -0500 (CDT)
Date: Wed, 14 Mar 2012 09:03:19 -0500 (CDT)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Mark Murawski <markm-lists@intellasoft.net>
In-Reply-To: <4F60266D.1090302@intellasoft.net>
Message-ID: <alpine.GSO.2.01.1203140858360.21564@freddy.simplesystems.org>
References: <4F5F7116.3020400@intellasoft.net>
	<4F5F97A4.6070000@brockmann-consult.de>
	<4F60266D.1090302@intellasoft.net>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Wed, 14 Mar 2012 09:03:20 -0500 (CDT)
Cc: freebsd-fs@freebsd.org
Subject: Re: ZFS file corruption problem
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: Wed, 14 Mar 2012 14:03:27 -0000

On Wed, 14 Mar 2012, Mark Murawski wrote:
>
> Why would the whole pool now become available upon access to a bad file?

A disk drive (or HBA) may be hanging (e.g. endless retries) when the 
bad file is accessed.  This is a common problem with consumer disks or 
HBAs which believe they are the top level authority when it comes to 
data integrity.  Zfs itself does not include any timers to decide to 
stop waiting.  Zfs depends on the lower-level OS & drivers to decide 
to stop waiting on a stalled device.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/