From owner-freebsd-fs@FreeBSD.ORG  Fri Apr  1 10:40:15 2011
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 2FF2E106566B;
	Fri,  1 Apr 2011 10:40:15 +0000 (UTC)
	(envelope-from petefrench@ingresso.co.uk)
Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk
	[IPv6:2001:470:1f09:176e::3])
	by mx1.freebsd.org (Postfix) with ESMTP id EB8E98FC13;
	Fri,  1 Apr 2011 10:40:14 +0000 (UTC)
Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]
	helo=dilbert.ticketswitch.com)
	by constantine.ingresso.co.uk with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.73 (FreeBSD)) (envelope-from <petefrench@ingresso.co.uk>)
	id 1Q5blz-000Czm-Of; Fri, 01 Apr 2011 11:40:11 +0100
Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.74
	(FreeBSD)) (envelope-from <petefrench@ingresso.co.uk>)
	id 1Q5blz-00084y-NW; Fri, 01 Apr 2011 11:40:11 +0100
To: petefrench@ingresso.co.uk, trociny@freebsd.org
In-Reply-To: <86wrjj5xfm.fsf@in138.ua3>
Message-Id: <E1Q5blz-00084y-NW@dilbert.ticketswitch.com>
From: Pete French <petefrench@ingresso.co.uk>
Date: Fri, 01 Apr 2011 11:40:11 +0100
Cc: freebsd-fs@freebsd.org, pjd@freebsd.org, freebsd-current@freebsd.org,
	freebsd-stable@freebsd.org
Subject: Re: Any success stories for HAST + ZFS?
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: Fri, 01 Apr 2011 10:40:15 -0000

> Yes, you may hit it only on hast devices creation. The workaround is to avoid
> using 'hastctl role primary all', start providers one by one instead.

Interesting to note that I just hit a lockup in hast (the discs froze
up - could not run hastctl or zpool import, and could not kill
them). I have two hast devices instead of one, but I am starting them
individually instead of  using 'all'. The copde includes all the latest
patches which have gone into STABLE over the last few days, none of which
look particularly controversial!

I havent tried your atch yet, nor been able to reporduce the lockup, but
thought you might be interested to know that I also had problems with
multiple providers.

cheers,

-pete.