From owner-freebsd-current@FreeBSD.ORG Mon Nov 30 09:02:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 637FF1065670; Mon, 30 Nov 2009 09:02:34 +0000 (UTC) (envelope-from ltning@anduin.net) Received: from mail.anduin.net (mail.anduin.net [213.225.74.249]) by mx1.freebsd.org (Postfix) with ESMTP id 02C8C8FC17; Mon, 30 Nov 2009 09:02:33 +0000 (UTC) Received: from [89.8.83.111] (helo=[10.252.245.116]) by mail.anduin.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NF29N-0008KE-Ph; Mon, 30 Nov 2009 10:02:32 +0100 References: <20091129013026.GA1355@michelle.cdnetworks.com> <74BFE523-4BB3-4748-98BA-71FBD9829CD5@anduin.net> Message-Id: <68E8D279-408D-4B75-82CF-880CDE01D55F@anduin.net> From: =?utf-8?Q?Eirik_=C3=98verby?= To: Adrian Chadd In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable X-Mailer: iPhone Mail (7D11) Mime-Version: 1.0 (iPhone Mail 7D11) Date: Mon, 30 Nov 2009 10:03:01 +0100 Cc: "pyunyh@gmail.com" , "weldon@excelsusphoto.com" , "freebsd-current@freebsd.org" , Robert Watson , Gavin Atkinson Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2009 09:02:34 -0000 On 30. nov. 2009, at 09.50, Adrian Chadd wrote: > 2009/11/30 Eirik =C3=98verby : > >>> That URL works for me. So how much traffic is this box handling =20 >>> during >>> peak times? >> >> Depends how you define load. It's a storage box (14TB ZFS) with a =20 >> small handful of NFS clients pushing backup data to it .. So lots =20 >> of traffic in bytes/sec, but not many clients. > > Ok. > >> If you're referring to the Send-Q and Recv-Q values, they are zero =20= >> everywhere I can tell. > > Hm, I was. Ok. > >>> See if you have full socket buffers showing up in netstat -an. Have >>> you tweaked the socket/TCP send/receive sizes? I typically lock mine >>> down to something small (32k-64k for the most part) so I don't hit >>> mbuf exhaustion on very busy proxies. > >> I haven't touched any defaults except the mbuf clusters. What does =20= >> your sysctl.conf look like? > > I just set these: > > net.inet.tcp.sendspace=3D65536 > net.inet.tcp.recvspace=3D65536 > > I tweak a lot of other TCP stack stuff to deal with satellite > latencies; its not relevant here. > > I'd love to see where those mbufs are hiding and whether they're a > leak, or whether the NFS server is just pushing too much data out for I fact it's mostly receiving. Other boxes on the LAN (or other =20 internal subnets) are pushing data to it, rarely reading any except to =20= check status and clean up. > whatever reason. Actually, something I also set was this: > > # Handle slightly more packets per interrupt tick > net.inet.ip.intr_queue_maxlen=3D512 > > It was defaulting to 50 which wasn't fast enough for small packet =20 > loads. I'll try all those and then some, but I'm no optimist.. Might try on =20 different hardware later. Thanks, /Eirik > Adrian > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org=20 > " >