From owner-freebsd-net@FreeBSD.ORG Fri Dec 11 10:53:38 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAA5B1065672 for ; Fri, 11 Dec 2009 10:53:38 +0000 (UTC) (envelope-from john@traktor.dnepro.net) Received: from traktor.dnepro.net (roof1.dnepro.net [212.3.111.66]) by mx1.freebsd.org (Postfix) with ESMTP id 4B00A8FC0A for ; Fri, 11 Dec 2009 10:53:37 +0000 (UTC) Received: from traktor.dnepro.net (localhost [127.0.0.1]) by traktor.dnepro.net (8.14.3/8.14.3) with ESMTP id nBBAraRO060071 for ; Fri, 11 Dec 2009 12:53:36 +0200 (EET) (envelope-from john@traktor.dnepro.net) Received: (from john@localhost) by traktor.dnepro.net (8.14.3/8.14.3/Submit) id nBBArawl060070 for freebsd-net@freebsd.org; Fri, 11 Dec 2009 12:53:36 +0200 (EET) (envelope-from john) Date: Fri, 11 Dec 2009 12:53:36 +0200 From: Eugene Perevyazko To: "freebsd-net@freebsd.org" Message-ID: <20091211105336.GB40831@traktor.dnepro.net> Mail-Followup-To: "freebsd-net@freebsd.org" References: <20091211102928.GA40831@traktor.dnepro.net> <9F5E7B59-0CF1-47A7-BE85-41B2C9F0D22B@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9F5E7B59-0CF1-47A7-BE85-41B2C9F0D22B@gmail.com> User-Agent: Mutt/1.4.2.3i Subject: Re: How can I find the reason network writes fail with ENOMEM on 7.x? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Dec 2009 10:53:38 -0000 On Fri, Dec 11, 2009 at 08:37:29AM -0200, Victor Lima wrote: > Have you checked your memory integrity? Maybe you should consider > buying some more mem to that machine. Have you check with top(1) how > much memory is actually available when the write fails? > That's not the lack of virtual/physical memory - the host has some "free" and lots of "Inact" memory and uses no swap space yet. Can it be related to those sysctls? vm.kmem_size_scale: 3 vm.kmem_size_max: 335544320 vm.kmem_size_min: 0 vm.kmem_size: 335544320 -- Eugene Perevyazko