Machine unresponsive with cache_lock: blocked on... message

Matthew Dillon dillon at
Sun Mar 21 18:54:25 PDT 2010

:top from the fbsd box:
:Mem: 777M Active, 2365M Inact, 383M Wired, 26M Cache, 399M Buf, 395M Free
:Swap: 4096M Total, 4096M Free
:top from the DF box:
:Memory: 878M Active, 1962M Inact, 516M Wired, 146M Cache, 188M Buf, 6132K
:Swap: 4096M Total, 10M Used, 4086M Free

    Well, it kinda looks to me like there's nothing wrong.  Are you seeing
    excessive paging activity via systat -vm 1 ?  If you don't see excessive
    paging activity then the fact that data has been pushed to swap will not
    have any effect on machine performance.  It just means the machine flushed
    dirty data to swap so it could be marked clean.  The data could still
    be in memory, in fact.

					Matthew Dillon 
					<dillon at>

More information about the Bugs mailing list