Date: Mon, 20 Oct 2003 22:35:00 -0000 From: "Brian F. Feldman" <green@freebsd.org> To: "Peter Edwards" <pmedwards@eircom.net> Cc: current@freebsd.org Subject: Re: useful workaround and analysis of vnode-backed md deadlock Message-ID: <200310202234.h9KMYwvO076139@green.bikeshed.org> In-Reply-To: Message from "Peter Edwards" <pmedwards@eircom.net> <20030910182003.BF84744001@mx1.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Peter Edwards" <pmedwards@eircom.net> wrote: > Once the running buffer space exceeds a high threshold, the scheduler > is blocked, to be awakened when completed async writes bring it > under the low threshold. However, a large chunk of the running buf > space is sitting queued for the md thread to process. The md thread > can't continue without the vnode lock, so the running buffer space > will not fall, and the bufdaemon cannot continue without running > buffer space, so will never release the vnode lock. This coincides with what I just discovered on my system, as well; did you try the patch from my post several days ago that just excludes the buffer flushing daemons from being used to wait for runningbufspace starvation to end? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200310202234.h9KMYwvO076139>