On 18/02/2018 21:11, Kurt Jaeger wrote:
> Around the 14th, processes started to be killed for out of swapspace,
> even if the box had almost no load at all.
> pid 1056 (mutt), uid 104, was killed: out of swap space
> pid 536 (devd), uid 0, was killed: out of swap space
> pid 15093 (exim), uid 26, was killed: out of swap space
> pid 91868 (mutt), uid 104, was killed: out of swap space
> pid 1086 (sshd), uid 104, was killed: out of swap space
> Reboot of the box and waiting a few hours and the problem re-occured.
> The box has 32 GB RAM and 34 GB swap, which never was utilized
> beyond a few hundred MBs.
One situation that can cause out of swap errors is large amounts of
wired ram. Wired ram is memory that can't be swapped out. When you get
around 80 or 90% of physical ram wired you start seeing those errors.
You can see the amount of wired displayed in top or
sysctl vm.stats.vm.v_wire_count then times that by hw.pagesize
There is a vm.max_wired but it doesn't appear to be an enforced limit.
FreeBSD - the place to B...Software Developing
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"