Re: someone is eating massive menory

2009/4/8 Randy Bush <randy_at_psg.com>:
> amd64, 4g ram, geom mirror and zfs
>
> another amd64 4g system is not crashing but is being very sloggish for
> 3-5 minutes.
>
> work0.psg.com:/root# uname -a
> FreeBSD work0.psg.com 8.0-CURRENT FreeBSD 8.0-CURRENT #22: Mon Apr  6 01:41:51 UTC 2009
> root_at_work0.psg.com:/usr/obj/usr/src/sys/WORK0  amd64
>
> when midnight crons run, it's death.  this is from serial console
>
> swap_pager_getswapspace(9): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(16): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(16): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(3): failed
>

If your system survived you could grep /var/log/messages
for processes killed by kernel.
That'd help you to find the guilty procs eating all memory.
Look at vm_pageout.c.


-- 
wbr,
pluknet