From owner-freebsd-net@FreeBSD.ORG Fri Jun 12 17:57:58 2015 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C69D72B; Fri, 12 Jun 2015 17:57:58 +0000 (UTC) (envelope-from csforgeron@gmail.com) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69B6E37E; Fri, 12 Jun 2015 17:57:58 +0000 (UTC) (envelope-from csforgeron@gmail.com) Received: by qcjl8 with SMTP id l8so12749281qcj.3; Fri, 12 Jun 2015 10:57:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bw1g5FKGOLozFitchMc98UqhUz6xgejCGsYDlzvbPNY=; b=ZXfPusRz1BtWsQDSDhE+HIBdInT/+4vCxG8w2NFSo5C/ZApMClLa6YYxH2ZGNVQqnd vgkWy6UjwJAz8hlpvXnmCg8F+j54BEC/oRqfgf/slAoKqeSZQBoSdd3nvG0r4hZHD0P3 SF4adTfxTCEQobZ4RyBaB3ffPD3lRDVpMOuxt7snRirZ9n0tXHxs3MmkOrd7bMhWYVu6 6R4hLQ+/X2zh0QvEYlJ83caLELA0hKLLrOYYLmjwOqJZFUIE1OwGmeeRRsmP72kRHIin DtxtUfnXWIunWiyOwdIwjpkRBKXnYcUN1vGLlA2agJv1JZzDyrs4gQfL4EbJbaxL8dae ivKw== MIME-Version: 1.0 X-Received: by 10.55.16.74 with SMTP id a71mr33201413qkh.15.1434131877441; Fri, 12 Jun 2015 10:57:57 -0700 (PDT) Received: by 10.96.76.104 with HTTP; Fri, 12 Jun 2015 10:57:57 -0700 (PDT) In-Reply-To: References: <374339249.53058039.1433681874571.JavaMail.root@uoguelph.ca> <55744F28.5000402@field.hu> <557AB1BB.60502@field.hu> <557AD10D.5070205@field.hu> <557AD2FA.103@field.hu> Date: Fri, 12 Jun 2015 14:57:57 -0300 Message-ID: Subject: Re: FreeBSD 10.1-REL - network unaccessible after high traffic From: Christopher Forgeron To: Adrian Chadd Cc: Cs , FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2015 17:57:58 -0000 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 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 >