Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Aug 2006 06:11:14 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        "Morten A. Middelthon" <morten@freenix.no>
Cc:        stable@freebsd.org, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: NFS locking question
Message-ID:  <20060815101114.GA51674@xor.obsecurity.org>
In-Reply-To: <20060815095950.GD34840@freenix.no>
References:  <20060228101453.GB47953@hugo10.ka.punkt.de> <20060228102150.GA56625@xor.obsecurity.org> <20060815095950.GD34840@freenix.no>

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

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

On Tue, Aug 15, 2006 at 11:59:50AM +0200, Morten A. Middelthon wrote:
> On Tue, Feb 28, 2006 at 05:21:50AM -0500, Kris Kennaway wrote:
> > On Tue, Feb 28, 2006 at 11:14:53AM +0100, Patrick M. Hausen wrote:
> > > Hi, all!
> > >=20
> > > In our local office network we have a rather old FreeBSD 5.2.1
> > > server acting as an NFS server for several other systems, mostly
> > > running 6.0.
> > >=20
> > > >From time to time we experience processes on the NFS clients
> > > hanging in statd "D" with wchan "lockd" when accessing files
> > > over NFS.
> >=20
> > Try the attached patch on the 6.0 machines:
> >=20
> > Index: usr.sbin/rpc.lockd/lock_proc.c
> <snip>
>=20
> Hi,
>=20
> I have been plagued with this NFS lockd issue for quite some time now. It=
 has
> kept me from installing FreeBSD 6.x on our workstations at work. I just t=
ried
> applying your patch to my own 6.1-RELEASE-p3 workstation, and so far it h=
as
> been working nicely. Has anyone else had the same experience? If so, mayb=
e it
> should go into production?

I was unable to obtain confirmation from anyone else (including the
submitter who previously claimed it was necessary, and my own testing)
that the patch actually solved a problem.  Since it involves reverting
useful functionality, someone would need to obtain further debugging
from your system (tcpdump traces before/after, etc) to determine what
it's actually solving.

Kris

--pf9I7BMVVzbSWLtt
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFE4Z3CWry0BWjoQKURAkhUAJ9xxVuuP4ptHmSdQu977GlL3zzByQCeLBmE
eRZ9uPxpWzB/oebgGnEOzts=
=oef8
-----END PGP SIGNATURE-----

--pf9I7BMVVzbSWLtt--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060815101114.GA51674>