From owner-freebsd-fs@FreeBSD.ORG  Tue Feb  8 11:00:28 2011
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 314FA106566C
	for <freebsd-fs@hub.freebsd.org>; Tue,  8 Feb 2011 11:00:28 +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 06A828FC17
	for <freebsd-fs@hub.freebsd.org>; Tue,  8 Feb 2011 11:00:28 +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 p18B0RWT096454
	for <freebsd-fs@freefall.freebsd.org>; Tue, 8 Feb 2011 11:00:27 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p18B0RFq096430;
	Tue, 8 Feb 2011 11:00:27 GMT (envelope-from gnats)
Date: Tue, 8 Feb 2011 11:00:27 GMT
Message-Id: <201102081100.p18B0RFq096430@freefall.freebsd.org>
To: freebsd-fs@FreeBSD.org
From: Carl <k0802647@telus.net>
Cc: 
Subject: Re: kern/154228: [md] md getting stuck in wdrain state
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Carl <k0802647@telus.net>
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, 08 Feb 2011 11:00:28 -0000

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

From: Carl <k0802647@telus.net>
To: bug-followup@FreeBSD.org, k0802647@telus.net
Cc:  
Subject: Re: kern/154228: [md] md getting stuck in wdrain state
Date: Tue, 08 Feb 2011 02:59:41 -0800

 For whatever reason I was not copied on the patch message, despite being 
 the bug reporter.
 
 The explanation for that patch is more than a little obscure. In simpler 
 terms, what have you uncovered?
 
 Does that patch implement a complete fix, partial fix, a workaround, or 
 what? Is it recommended I try it?
 
 Did someone manage to reproduce my problem scenario?
 
 Yesterday I ran into the same bug. Similar but different exercise. Again 
 on a remote production system. I had no choice but to try again, so I 
 repeated the procedure, only using a non-sparse file instead. It hung 
 yet again, so that should rule out sparse files as part of the problem.
 
 I noticed in the mdconfig(8) man page this description for the "-o 
 [no]async" option:
 
    'For vnode backed devices: avoid IO_SYNC for increased
     performance but at the risk of deadlocking the entire
     kernel.'
 
 It seems to me the default would be "-o noasync" and that this is 
 supposed to avoid that particular risk for deadlock, but what command 
 can I use to verify whether a particular enabled memory disk is actually 
 using IO_SYNC or not?
 
 Carl                                                   / K0802647