From owner-freebsd-current@FreeBSD.ORG Fri Jan 8 22:01:14 2010 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 A3246106568D; Fri, 8 Jan 2010 22:01:14 +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 573A68FC08; Fri, 8 Jan 2010 22:01:14 +0000 (UTC) Received: from [212.62.248.147] (helo=ranger.home.anduin.net) by mail.anduin.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NTMtK-0005ZU-G4; Fri, 08 Jan 2010 23:01:10 +0100 Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=iso-8859-1 From: =?iso-8859-1?Q?Eirik_=D8verby?= In-Reply-To: Date: Fri, 8 Jan 2010 23:01:09 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20091129013026.GA1355@michelle.cdnetworks.com> <74BFE523-4BB3-4748-98BA-71FBD9829CD5@anduin.net> <34AD565D-814A-446A-B9CA-AC16DD762E1B@anduin.net> <1DFC4992-E136-4674-BC0E-A6B1DAE12AF4@anduin.net> <3BC13C71-348A-49AD-94BA-FC28EB0648DE@freebsd.org> <43D0E400-183E-4741-9ABD-14ED80D90983@anduin.net> To: Rick Macklem X-Mailer: Apple Mail (2.1077) Cc: pyunyh@gmail.com, weldon@excelsusphoto.com, freebsd-current@freebsd.org, "Robert N. M. 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: Fri, 08 Jan 2010 22:01:14 -0000 On 8. jan. 2010, at 22.48, Rick Macklem wrote: > On Fri, 8 Jan 2010, Eirik =C3~Xverby wrote: >=20 >>=20 >> On 8. jan. 2010, at 16.33, Robert N. M. Watson wrote: >>> On 30 Nov 2009, at 19:13, Eirik =D8verby wrote: >>>=20 >>>> I meant NFS-UDP ... However I was wrong even there; Using NFS over = UDP from FreeBSD boxes does not cause the same issue. So OpenBSD seems = to be a special case here. >>>>=20 > As a data point, I tried to reproduce it here using an OpenBSD4.5 = client and wasn't able to see a leak. So it might be only certain = versions of > OpenBSD or certain network configs or ??? (I used NFSv3 over UDP.) >=20 > I doubt it, but if the version of OpenBSD you were using happened to > use NFSv2 by default with UDP vs NFSv3 for TCP, there is a patch that > fixes an mbuf leak, that is specific to NFSv2. However, if you were > using NFSv3 over UDP, then this won't be relevant. 10.1.5.200:/data/backup/alge.anart.no on /mnt type nfs (v3, tcp, = timeo=3D100) 10.1.5.200:/data/backup/alge.anart.no on /mnt2 type nfs (v3, udp, = timeo=3D100) The first one is the mount I'm currently using (v3, tcp), which does not = cause the problem. The second one is the result of mount 10.1.5.200:/data/backup/alge.anart.no /mnt2 and it does, though it's OpenBSD 4.4, default to v3 udp. I'll try gathering a trace next week. Any other ideas, let me know. /Eirik > I can look at a packet trace, but I kinda doubt that it's going to > shed light on the cause of the mbuf leak. > ("tcpdump -s 0 -w host " should get a packet capture > that Wireshark will make sense of.) >=20 > rick > _______________________________________________ > 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"