No subject

Unknown Unknown
Sat Mar 20 13:42:32 PDT 2010

8.GA1575 at>
From: Matthew Dillon <dillon at>
Subject: Re: Machine unresponsive with cache_lock: blocked on... message
Date: Sat, 20 Mar 2010 13:41:54 -0700 (PDT)
List-Post: <mailto:bugs at>
List-Subscribe: <mailto:bugs-request at>
List-Unsubscribe: <mailto:bugs-request at>
List-Help: <mailto:bugs-request at>
List-Owner: <mailto:owner-bugs at>
Sender: bugs-errors at
Errors-To: bugs-errors at
Lines: 18
X-Trace: 1269117830 55377
Xref: dragonfly.bugs:11540

:Okay. Since this is not really something which can be resolved automatically,
:is there a way for the administrator to set a hard limit to the memory used
:by disk activity ?
:A sysctl such as kern.max_disk_cache or so ?
:Francois Tigeot

    Being able to predict that a piece of data does not have to be cached
    for very long, such as when traversing a very large data set (rdist,
    rebalance, reblock) is what allows the rest of the data in the cache to
    remain in the cache.  This is not an easy prediction to make.  Something
    like an ARC implementation would do a better job making this prediction.

					Matthew Dillon 
					<dillon at>

More information about the Bugs mailing list