Date: Fri, 12 Jun 2015 11:17:42 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Christopher Forgeron <csforgeron@gmail.com> Cc: Cs <bimmer@field.hu>, FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: FreeBSD 10.1-REL - network unaccessible after high traffic Message-ID: <CAJ-Vmo=hSE%2Bk1q_JrX9wKOshSRa_WJ78hbL54ZaXMH03PrNFdg@mail.gmail.com> In-Reply-To: <CAB2_NwANWRB2SJY0rO7n%2B_8RK61dyGJ5FCphH_ewQG-E7eOAUg@mail.gmail.com> References: <374339249.53058039.1433681874571.JavaMail.root@uoguelph.ca> <55744F28.5000402@field.hu> <CAB2_NwA-D7bH47=Qkf9QLF3=mZOQBVo81bUsQzQr02W9U4vHMA@mail.gmail.com> <557AB1BB.60502@field.hu> <CAB2_NwA9i-wMXGH2%2BcP9SWxDMNomFRjoVP25hsGWaTDGjBxFTw@mail.gmail.com> <557AD10D.5070205@field.hu> <CAB2_NwAeD43tSwWO3LGuniRMNZ3TVupOuLWj3aUm228jLT2y1A@mail.gmail.com> <557AD2FA.103@field.hu> <CAB2_NwCgEvmMxqmAotO1USsipXOSaGkwK3Uu%2BiVbKd9_bn%2BLWg@mail.gmail.com> <CAJ-VmokXk69V_YURWOjLOQmKrW%2B2-YAiFQnhLOA7SKO6ipw_KQ@mail.gmail.com> <CAB2_NwANWRB2SJY0rO7n%2B_8RK61dyGJ5FCphH_ewQG-E7eOAUg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 June 2015 at 10:57, Christopher Forgeron <csforgeron@gmail.com> wrote: > 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. > Hi, Then something is leaking or holding onto memory when it shouldn't be. Try doing vmstat -z and vmstat -m in a one second loop, post the data just before it falls over. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=hSE%2Bk1q_JrX9wKOshSRa_WJ78hbL54ZaXMH03PrNFdg>