From owner-freebsd-fs@FreeBSD.ORG  Sun Jan 23 19:10:38 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 328F41065675;
	Sun, 23 Jan 2011 19:10:38 +0000 (UTC) (envelope-from kib@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 08F2B8FC17;
	Sun, 23 Jan 2011 19:10:38 +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 p0NJAbFo018892;
	Sun, 23 Jan 2011 19:10:37 GMT
	(envelope-from kib@freefall.freebsd.org)
Received: (from kib@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0NJAbaU018853;
	Sun, 23 Jan 2011 19:10:37 GMT (envelope-from kib)
Date: Sun, 23 Jan 2011 19:10:37 GMT
Message-Id: <201101231910.p0NJAbaU018853@freefall.freebsd.org>
To: k0802647@telus.net, kib@FreeBSD.org, freebsd-amd64@FreeBSD.org,
	freebsd-fs@FreeBSD.org
From: kib@FreeBSD.org
Cc: 
Subject: Re: amd64/154228: md getting stuck in wdrain state
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: Sun, 23 Jan 2011 19:10:38 -0000

Synopsis: md getting stuck in wdrain state

State-Changed-From-To: open->feedback
State-Changed-By: kib
State-Changed-When: Sun Jan 23 19:08:34 UTC 2011
State-Changed-Why: 
Apparently, the suspension of the filesystem failed to finish, causing
all writers on the filesystem to block.

To diagnose the cause, we need the information specified at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html


Responsible-Changed-From-To: freebsd-amd64->freebsd-fs
Responsible-Changed-By: kib
Responsible-Changed-When: Sun Jan 23 19:08:34 UTC 2011
Responsible-Changed-Why: 
UFS issue.

http://www.freebsd.org/cgi/query-pr.cgi?pr=154228