From owner-freebsd-fs@FreeBSD.ORG Mon Jan 24 03:26:29 2011 Return-Path: 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 F4139106566B for ; Mon, 24 Jan 2011 03:26:28 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 9D1708FC08 for ; Mon, 24 Jan 2011 03:26:28 +0000 (UTC) Received: (qmail 12005 invoked by uid 399); 24 Jan 2011 03:26:26 -0000 Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 24 Jan 2011 03:26:26 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4D3CF161.8040906@FreeBSD.org> Date: Sun, 23 Jan 2011 19:26:25 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101210 Thunderbird/3.1.7 MIME-Version: 1.0 To: Carl References: <201101232350.p0NNoB2o016577@freefall.freebsd.org> In-Reply-To: <201101232350.p0NNoB2o016577@freefall.freebsd.org> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org 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 List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 03:26:29 -0000 On 01/23/2011 15:50, Carl wrote: > The following reply was made to PR kern/154228; it has been noted by GNATS. > > From: Carl > To: bug-followup@FreeBSD.org, k0802647@telus.net > Cc: > Subject: Re: kern/154228: [md] md getting stuck in wdrain state > Date: Sun, 23 Jan 2011 15:08:15 -0800 > > Now I owe a friend a beer. Make it a good one. :) > His assertion was that in submitting this bug > report I would incur a request to use a debugger myself, and this > despite me being an end user reporting a problem on a production system > in a remote location which other people depend on. > > While it would be an interesting and educational distraction to rebuild > the kernel and deadlock a production system a few more times, I trust > it's understood why that can't happen. As such, I thought it would be > helpful to provide the above script so FreeBSD developers with more > systems at their disposal might try to reproduce the problem. Any chance > of that happening? Is there _any_ chance of it? Maybe. However experience says that problems like the one you're reporting are generally very environment dependent, and if no one has jumped at the opportunity yet then it's not likely to happen, or at least not soon. Not to put too fine a point on it, but doing your part in situations like this is part of the "cost" of "free" software. Good luck, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/