Date: Sun, 23 Jan 2011 23:50:11 GMT From: Carl <k0802647@telus.net> To: freebsd-fs@FreeBSD.org Subject: Re: kern/154228: [md] md getting stuck in wdrain state Message-ID: <201101232350.p0NNoB2o016577@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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: Sun, 23 Jan 2011 15:08:15 -0800 Now I owe a friend a beer. 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? Carl / K0802647
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101232350.p0NNoB2o016577>