Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 Jul 2006 07:58:54 +0300
From:      Kostik Belousov <kostikbel@gmail.com>
To:        Francisco Reyes <lists@stringsutils.com>
Cc:        freebsd-stable@freebsd.org, User Freebsd <freebsd@hub.org>
Subject:   Re: NFS Locking Issue
Message-ID:  <20060703045854.GH37822@deviant.kiev.zoral.com.ua>
In-Reply-To: <cone.1151902211.613551.64011.1000@zoraida.natserv.net>
References:  <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <cone.1151802806.162227.42680.1000@zoraida.natserv.net> <20060702162942.D1103@ganymede.hub.org> <cone.1151876984.69254.64011.1000@zoraida.natserv.net> <20060703042010.GG37822@deviant.kiev.zoral.com.ua> <cone.1151902211.613551.64011.1000@zoraida.natserv.net>

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

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

On Mon, Jul 03, 2006 at 12:50:11AM -0400, Francisco Reyes wrote:
> Kostik Belousov writes:
> >Since nobody except you experience that problems (at least, only you=20
> >notified
> >about the problem existence)
>=20
> Did you miss the part of:
>=20
> >User Freebsd writes:
> >>Since there are several of us experiencing what looks to be the same so=
rt
> >>of deadlock issue, I beseech you not to give up
>=20
> I am not the only one reporting or having the issue.
I think you have different issues.
>=20
> >Is this for intr mounts?
>=20
> "intr" ?
Mount option that allows to interrupt nfs operation by signal.
See mount_nfs(8). BTW, I had the impression that this feature not working
was one of your problem.
>=20
>=20
> >improved handling of signals in nfs client. If you could test it, that
> >would be useful.
>=20
> Does it matter if the OS is i386 or am64?
> Have an amd64 machine I can more easily play with... with no risk to=20
> production.=20
No, this shall be applicable to any arch. Except that the patches are sever=
al
month old, and were developed against CURRENT. But I think that it is
applicable to STABLE.

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

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

iD8DBQFEqKQOC3+MBN1Mb4gRAgUsAKC7Beb/cDcHREvTCKjxWCOxoQH10gCghB2+
K8NvD2dD4XTpC4zS359qvIo=
=ju7V
-----END PGP SIGNATURE-----

--PyMzGVE0NRonI6bs--



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