From owner-freebsd-fs@FreeBSD.ORG  Sun Feb 28 14:56:08 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D2379106566B;
	Sun, 28 Feb 2010 14:56:08 +0000 (UTC)
	(envelope-from rwatson@freebsd.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id A251F8FC23;
	Sun, 28 Feb 2010 14:56:08 +0000 (UTC)
Received: from [192.168.2.102] (host86-181-230-35.range86-181.btcentralplus.com
	[86.181.230.35])
	by cyrus.watson.org (Postfix) with ESMTPSA id 348D146B29;
	Sun, 28 Feb 2010 09:56:07 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: "Robert N. M. Watson" <rwatson@freebsd.org>
In-Reply-To: <E1NlkVg-00068M-Qk@kabab.cs.huji.ac.il>
Date: Sun, 28 Feb 2010 14:56:05 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEA988DB-9925-4695-98C6-E5B484FDAD1A@freebsd.org>
References: <20100226174021.8feadad9.gerrit@pmp.uni-hannover.de>
	<E1Nl6VA-000557-D9@kabab.cs.huji.ac.il>
	<20100226224320.8c4259bf.gerrit@pmp.uni-hannover.de>
	<4B884757.9040001@digiware.nl>
	<20100227080220.ac6a2e4d.gerrit@pmp.uni-hannover.de>
	<4B892918.4080701@digiware.nl>
	<20100227202105.f31cbef7.gerrit@pmp.uni-hannover.de>
	<20100227193819.GA60576@icarus.home.lan>
	<BD8AC9F6-DF96-41F9-8E92-48A4E5606DC7@anduin.net>
	<4B89943C.70704@digiware.nl>
	<20100227220310.GA65110@icarus.home.lan>
	<E1Nlhzr-0004ci-3W@kabab.cs.huji.ac.il>
	<F794BAF9-4ADC-48F8-ACC3-C441EF77A8F2@freebsd.org>
	<E1NlkVg-00068M-Qk@kabab.cs.huji.ac.il>
To: Daniel Braniss <danny@cs.huji.ac.il>
X-Mailer: Apple Mail (2.1077)
Cc: stable@freebsd.org, freebsd-fs@freebsd.org,
	Willem Jan Withagen <wjw@digiware.nl>,
	=?iso-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net>,
	Jeremy Chadwick <freebsd@jdc.parodius.com>
Subject: Re: mbuf leakage with nfs/udp (was: mbuf leakage with nfs/zfs)
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Feb 2010 14:56:08 -0000


On Feb 28, 2010, at 2:52 PM, Daniel Braniss wrote:

> well, I have further reduced the problem, it happens with NFS/UDP =
writes.
> i'll try the wireshark road, but i'm very rusty with RPC, the other =
road is to
> check the changes, my oldest is from late october (RC2) where it's =
happening,=20
> while
> Gerrit tried 8-pre from November and worked, so it will be fun
> trying to nail it down :-)

Fortunately, Wireshark actually has quite a good NFS RPC decoder -- it =
will tell you what operation appears, what the arguments are, interpret =
NFS error codes, etc. In fact, it's an excellent way to learn about =
NFS...

Robert=