From owner-freebsd-stable@FreeBSD.ORG  Wed May 14 20:20:44 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3140E1065670
	for <freebsd-stable@freebsd.org>; Wed, 14 May 2008 20:20:44 +0000 (UTC)
	(envelope-from aragon@phat.za.net)
Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81])
	by mx1.freebsd.org (Postfix) with ESMTP id D18078FC1B
	for <freebsd-stable@freebsd.org>; Wed, 14 May 2008 20:20:43 +0000 (UTC)
	(envelope-from aragon@phat.za.net)
Received: by mail.geek.sh (Postfix, from userid 1000)
	id 77C3C24D26; Wed, 14 May 2008 22:20:42 +0200 (SAST)
Date: Wed, 14 May 2008 22:20:42 +0200
From: Aragon Gouveia <aragon@phat.za.net>
To: freebsd-stable@freebsd.org
Message-ID: <20080514202042.GA23704@phat.za.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386
Subject: instability with gmirror and atacontrol spindown
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 May 2008 20:20:44 -0000

Hi,

I eagerly started using atacontrol's new spindown command the other day. 
There's a gmirror volume running on top of the two disks that get spundown. 
I find that often when the drives are spun back up to serve a disk request,
one of the ata devices times out and my system goes into a never ending loop
of retrying.  At that point I'm lucky if I'm able to shutdown gracefully.

This is what is logged on the console after the disk spin up message:

ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing
request directly
ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing 
request directly
ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing
request directly
ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing
request directly
ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly
ad8: TIMEOUT - READ_DMA retrying (1 retry left) LBA=20047817
ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing 
request directly
ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing 
request directly
ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing
request directly
ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing
request directly
ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly
ad8: TIMEOUT - READ_DMA retrying (0 retries left) LBA=20047817
<rinse and repeat>

I can only reproduce it when my gmirror volume is running.

Any ideas?


Thanks,
Aragon