Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Jan 2010 23:01:09 +0100
From:      =?iso-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        pyunyh@gmail.com, weldon@excelsusphoto.com, freebsd-current@freebsd.org, "Robert N. M. Watson" <rwatson@freebsd.org>, Gavin Atkinson <gavin@freebsd.org>
Subject:   Re: FreeBSD 8.0 - network stack crashes?
Message-ID:  <E0A53478-1D31-4D46-AC7A-01E94C7A73FB@anduin.net>
In-Reply-To: <Pine.GSO.4.63.1001081642560.24198@muncher.cs.uoguelph.ca>
References:  <A1648B95-F36D-459D-BBC4-FFCA63FC1E4C@anduin.net> <20091129013026.GA1355@michelle.cdnetworks.com> <74BFE523-4BB3-4748-98BA-71FBD9829CD5@anduin.net> <alpine.BSF.2.00.0911291427240.80654@fledge.watson.org> <34AD565D-814A-446A-B9CA-AC16DD762E1B@anduin.net> <A0C9ED20-5536-44E2-B26B-0F1AEC2AF79C@anduin.net> <BA47FDA1-1097-4C43-AF71-51E7227795B5@FreeBSD.org> <1DFC4992-E136-4674-BC0E-A6B1DAE12AF4@anduin.net> <EE2AA268-2309-4924-A3AD-1EC256E7BB2A@freebsd.org> <E8883290-0D35-44AC-9ED9-8464C4F7FF62@anduin.net> <3BC13C71-348A-49AD-94BA-FC28EB0648DE@freebsd.org> <43D0E400-183E-4741-9ABD-14ED80D90983@anduin.net> <Pine.GSO.4.63.1001081642560.24198@muncher.cs.uoguelph.ca>

next in thread | previous in thread | raw e-mail | index | archive | help

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 <file> host <server>" 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"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0A53478-1D31-4D46-AC7A-01E94C7A73FB>