Bug 123936

Comment 1 Kris Kennaway 2008-05-23 23:59:14 UTC

On Fri, May 23, 2008 at 07:17:48PM +0200, Stefan `Sec` Zehl wrote:
> 
> >Number:         123936
> >Category:       amd64
> >Synopsis:       Swap problem?
> >Confidential:   no
> >Severity:       serious
> >Priority:       low
> >Responsible:    freebsd-amd64
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Fri May 23 17:20:00 UTC 2008
> >Closed-Date:
> >Last-Modified:
> >Originator:     Stefan `Sec` Zehl
> >Release:        FreeBSD 7.0-STABLE amd64
> >Organization:
> >Environment:
> System: FreeBSD ice 7.0-STABLE FreeBSD 7.0-STABLE #13: Thu May 8 15:00:23 CEST 2008 root@ice:/usr/obj/usr/src/sys/ICE amd64
> 
> 
> 	
> >Description:
> 
> My FreeBSD-7.0-STABLE amd64 machine had some strange swap problems today.
> 
> /var/log/messages shows these messages:
> 
> | May 23 10:59:07 ice kernel: swap_pager_getswapspace(16): failed
> | May 23 10:59:07 ice kernel: swap_pager_getswapspace(8): failed
> | May 23 10:59:07 ice kernel: swap_pager_getswapspace(16): failed
> | May 23 10:59:07 ice kernel: swap_pager_getswapspace(12): failed
> | May 23 10:59:07 ice kernel: swap_pager_getswapspace(16): failed
> | May 23 10:59:07 ice kernel: swap_pager_getswapspace(12): failed
> | May 23 10:59:07 ice kernel: swap_pager_getswapspace(16): failed
> | [....]
> until two processes were killed
> 
> | May 23 10:59:11 ice kernel: pid 52947 (named), uid 53, was killed: out of swap s
> 
> After that, these messages stopped.
> 
> The disk itself appears to be ok -- smartctl lists no problems(did also run a
> smartctl -t short run), and a dd can read the entire swap device without
> problems.
> 
> I have encrypted my swap by having the following line in my /etc/fstab:
> |/dev/ad4s1b.eli         none            swap    sw              0       0
> 
> swapinfo confirms this:
> | Device          1K-blocks     Used    Avail Capacity
> | /dev/ad4s1b.eli   1441088   188852  1252236    13%
> 
> Is there any known issue with encrypted swap? And do the numbers in
> "getspace(xx)" signify anyting? Is there any additional information needed?

This is not a bug.  Your system ran out of free swap, reported the
failure to allocate more of it, then killed off one of the processes
that was hogging it.

Kris

Comment 2 Kris Kennaway 2008-05-23 23:59:21 UTC

State Changed
From-To: open->closed

Submitter needs to add more swap or reduce the demand for it.