From owner-freebsd-current@FreeBSD.ORG Thu Oct 30 14:52:19 2003 Return-Path: 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 B823416A4D4 for ; Thu, 30 Oct 2003 14:52:19 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCF8F43FBD for ; Thu, 30 Oct 2003 14:52:18 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 8D85966C9E; Thu, 30 Oct 2003 14:52:18 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 73841876; Thu, 30 Oct 2003 14:52:18 -0800 (PST) Date: Thu, 30 Oct 2003 14:52:18 -0800 From: Kris Kennaway To: Soren Schmidt Message-ID: <20031030225218.GA31347@rot13.obsecurity.org> References: <3F9E4CC3.30706@xtaz.co.uk> <200310281107.h9SB79mb006396@spider.deepcore.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <200310281107.h9SB79mb006396@spider.deepcore.dk> User-Agent: Mutt/1.4.1i cc: current@FreeBSD.ORG Subject: Re: Still gettnig NFS client locking up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 30 Oct 2003 22:52:20 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 28, 2003 at 12:07:09PM +0100, Soren Schmidt wrote: > It seems Matt wrote: > > I'm now running a kernel/world of October 26th on both NFS client and= =20 > > server machines. I am still seeing NFS lockups as reported by several= =20 > > people in these threads: > >=20 > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D1296172+0+archive/2003/f= reebsd-current/20031026.freebsd-current > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D1333116+0+archive/2003/f= reebsd-current/20031026.freebsd-current > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D1477462+0+archive/2003/f= reebsd-current/20031026.freebsd-current > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D1469939+0+archive/2003/f= reebsd-current/20031026.freebsd-current > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D1467159+0+archive/2003/f= reebsd-current/20031026.freebsd-current > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D1314547+0+archive/2003/f= reebsd-current/20031026.freebsd-current > >=20 > > I just tried port upgrading bind9 and it got 10% through downloading an= d=20 > > locked up. I tried an ls /usr/ports and there was no response. I had to= =20 > > umount -f /usr/ports to get the processes to exit. > >=20 > > Poul-Henning's patch did not have any effect because it appears to be= =20 > > the client at fault not the server as Marc Olzheim mentioned that he ha= s=20 > > the same issue with a 4.x NFS server machine using a 5.1-current client. >=20 > Me too!! I've reported NFS corruption on certain p4 machines running 5.x, which may or may not be related. No lockups though. Kris --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/oZYiWry0BWjoQKURAttNAJsEAjXTeSSXDAdSnOdJM36WHDuWcgCgzzTy dOH3lgANT0iQMLv+2Z5a/Tk= =x2c5 -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv--