From owner-freebsd-net@FreeBSD.ORG Fri Jun 12 18:17:43 2015 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9723B9F2 for ; Fri, 12 Jun 2015 18:17:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (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 59697A1A for ; Fri, 12 Jun 2015 18:17:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iebgx4 with SMTP id gx4so29307502ieb.0 for ; Fri, 12 Jun 2015 11:17:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=QQ5tWgZtiFJn8ZHOMro6X0vvG4PDhhmLmtojpBFMX0s=; b=EcwavyOB1YQjSzogyMwuvL8/JR/s5seEjV95Rfw0gGs1Ex5C5/toHnPSikyiqlFNbZ yWSTOE71rc0l+oijJpJPhkkmzcdk4ObEhOcLIR9baXOY2tIzNjHPW+DBwIqN3ompnGXJ dhiLBkk5lc4dcHXJhcSVHadc7hCrm9pnukL2nWYNuS1lltIJeGdOck62cEUVyIYoawPv eBHCuhQOzs5UGksyzaWatAYewkiWFGrwPcrGQf9wZBzDH5JZUrVxLq+zX00sbW4T5J5L rjhKXf2WlQbSKZ6pPT9HGoX5AUSyQqVVP1GTVw/NUpG7SmDemUgESR3dMXDSC4jqlYLi ftNw== MIME-Version: 1.0 X-Received: by 10.50.111.167 with SMTP id ij7mr5993308igb.49.1434133062742; Fri, 12 Jun 2015 11:17:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.38.133 with HTTP; Fri, 12 Jun 2015 11:17:42 -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 11:17:42 -0700 X-Google-Sender-Auth: _cWyBNhPIVlWGomjg2ViMsGTrKA Message-ID: Subject: Re: FreeBSD 10.1-REL - network unaccessible after high traffic From: Adrian Chadd To: Christopher Forgeron Cc: Cs , FreeBSD Net Content-Type: text/plain; charset=UTF-8 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 18:17:43 -0000 On 12 June 2015 at 10:57, Christopher Forgeron 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