:I had the same symptoms with a runaway openjdk7 program, where
:killing/restarting the program on a regular basis would keep it from
:happening... but I never caught a high usage on swap.
:
:On Wed, Feb 26, 2014 at 12:29 AM, lhmwzy <[email protected]> wrote:
:
:> It has serveral times run into no responese problem.
:> the console messages are:
:> cache_lock blocked on 0xffffffe085065430 80000001 "blocklist.RSA-2048"
:> swap_pager: indefinite wait buffer: offset: 416837632,size:4096
:> swap_pager: indefinite wait buffer: offset: 416837632,size:4096
:> swap_pager: indefinite wait buffer: offset: 416837632,size:4096
:> swap_pager: indefinite wait buffer: offset: 416837632,size:4096
:> swap_pager: indefinite wait buffer: offset: 416837632,size:4096
:> swap_pager: indefinite wait buffer: offset: 416837632,size:4096
:> swap_pager: indefinite wait buffer: offset: 416837632,size:4096
:> swap_pager: indefinite wait buffer: offset: 416837632,size:4096
:> swap_pager: indefinite wait buffer: offset: 416837632,size:4096
:> .....
An indefinite swap wait buffer typically means that the I/O is
stuck. Usually you see disk controller error messages along with
it, though.
Swap space is just an extension of anonymous memory, and is also
used by swapcache. If swapcache is turned off the only swap space
in use will be for pages of (dirty) memory which have been paged to
swap in order to free up the memory. A system typically always has
some swap usage due to things like idle 'getty' processes whos pages
are slowly swapped out (freeing the related memory for use by active
programs).
If swapcache is not being used and swap space use is excessive, there's
a runaway program somewhere eating up all your memory and swap.
-Matt
