Re: useful workaround and analysis of vnode-backed md deadlock

"Peter Edwards" <pmedwards_at_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_at_FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\