FreeBSD 10.1-REL - network unaccessible after high traffic

Christopher Forgeron csforgeron at gmail.com
Fri Jun 12 17:57:58 UTC 2015


I agree it shouldn't run out of memory. Here's what mine does under network
load, or rsync load:

2 0 9   1822M  1834M     0   0   0   0    14   8   0   0 22750  724 136119
0 23 77

0 0 9   1822M  1823M     0   0   0   0     0   8   0   0 44317  347 138151
0 16 84

0 0 9   1822M  1761M     0   0   0   0    17   8   0   0 23818  820 92198
0 12 88

0 0 9   1822M  1727M     0   0   0   0    14   8   0   0 40768  634 126688
0 17 83

0 0 9   1822M  8192B     0   8   0   0    15   3   3   0 9236  305 57149  0
33 67


That's with a 5 second vmstat output. After the 8KiB, the system is nearly
completely brain-dead and needs a hard power-off.


I've seen it go from 6 GiB free to 8KiB in 5 sec as well. Currently my
large machines are set to 12 GiB free to keep them from crashing, from what
I presume is just network load due to lots of iSCSI / NFS traffic on my
10GiB network.


I haven't had time to type this up for the list yet, but I'm putting it
here just to make sure people know it's real.




On Fri, Jun 12, 2015 at 1:12 PM, Adrian Chadd <adrian at freebsd.org> wrote:

> Hi,
>
> It shouldn't "run out of memory" like this in a way that pisses off
> em, not unless it's leaking memory and it can't allocate mbufs.
>
> netstat -m wil list mbuf allocations and what's failed.
>
> vmstat -z will list all the memory pools and which allocations have failed.
>
> Both would be good to post.
>
>
>
> -adrian
>


More information about the freebsd-net mailing list