From owner-freebsd-bugs@FreeBSD.ORG  Wed Sep  8 17:40:03 2010
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id BBEC710656B4
	for <freebsd-bugs@hub.freebsd.org>;
	Wed,  8 Sep 2010 17:40:03 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 913198FC08
	for <freebsd-bugs@hub.freebsd.org>;
	Wed,  8 Sep 2010 17:40:03 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o88He3pl064125
	for <freebsd-bugs@freefall.freebsd.org>; Wed, 8 Sep 2010 17:40:03 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o88He3cj064124;
	Wed, 8 Sep 2010 17:40:03 GMT (envelope-from gnats)
Date: Wed, 8 Sep 2010 17:40:03 GMT
Message-Id: <201009081740.o88He3cj064124@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Rich <rercola@acm.jhu.edu>
Cc: 
Subject: Re: misc/150390: zfs deadlock when arcmsr reports drive faulted
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Rich <rercola@acm.jhu.edu>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 17:40:03 -0000

The following reply was made to PR misc/150390; it has been noted by GNATS.

From: Rich <rercola@acm.jhu.edu>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: misc/150390: zfs deadlock when arcmsr reports drive faulted
Date: Wed, 8 Sep 2010 13:00:26 -0400

 A neat update:
 It's demonstrably the case that this only occurs when a disk is marked
 FAULTED - if you physically remove a disk while the system is booted,
 the disk is correctly removed from the list of disks in areca-cli, and
 ZFS reports write errors but behaves correctly.
 
 - Rich