From owner-freebsd-current@FreeBSD.ORG  Fri Feb  4 00:11:07 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4571A16A4CF; Fri,  4 Feb 2005 00:11:07 +0000 (GMT)
Received: from obsecurity.dyndns.org
	(CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 06CCF43D46; Fri,  4 Feb 2005 00:11:07 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id AECF85146E; Thu,  3 Feb 2005 16:11:05 -0800 (PST)
Date: Thu, 3 Feb 2005 16:11:05 -0800
From: Kris Kennaway <kris@obsecurity.org>
To: Mohan Srinivasan <mohan_srinivasan@yahoo.com>
Message-ID: <20050204001105.GA3760@xor.obsecurity.org>
References: <20050203180756.GA2103@xor.obsecurity.org>
	<20050203182917.40592.qmail@web80603.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v"
Content-Disposition: inline
In-Reply-To: <20050203182917.40592.qmail@web80603.mail.yahoo.com>
User-Agent: Mutt/1.4.2.1i
cc: ps@FreeBSD.org
cc: current@FreeBSD.org
cc: mohans <mohans@yahoo-inc.com>
cc: Kris Kennaway <kris@obsecurity.org>
Subject: Re: Processes stuck in nfsreq
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2005 00:11:07 -0000


--Dxnq1zWXvFF0Q93v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 03, 2005 at 10:29:16AM -0800, Mohan Srinivasan wrote:
> Hi,
>=20
> In the info you have below, the NFS request was not sent (R_SENT
> is not set). We didn't send out the request because possibly nm_cwnd=20
> didn't allow us to send the request. If nfs_request() could not send=20
> the request, then typically, the request would be retransmitted from=20
> nfs_timer().=20
>=20
> If nm_cwnd is full, then there must be a lot of outstanding requests=20
> that haven't been replied to yet (on this mount), which is the fundamental
> issue.

FYI, this is truly hung and not just backlogged - it hasn't proceeded
any further since last night.

> Can you force a core dump and send me a pointer to it ?

Unfortunately not, because twed dumping is still broken.  The only way
I was able to obtain this information is because kan has patches that
fix kgdb enough to use it on the running kernel.

> Also, after you force a core, can you also try a quick workaround - someo=
ne
> else also reported NFS client hangs and said that things were fine
> after they set mpsafenet to 0. It would be good to see if there's a
> correlation there.

I can try that.

Kris
--Dxnq1zWXvFF0Q93v
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCAr2ZWry0BWjoQKURAqV3AJ4wOuupBoGVf75mVJeSMDHb1tqHCACg7Tlq
xxU355GFq1yiU7zH/SI3HZM=
=Yazc
-----END PGP SIGNATURE-----

--Dxnq1zWXvFF0Q93v--