Date: Fri, 29 Sep 2006 13:29:54 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Yuri Khotyaintsev <yuri@irfu.se>, mohans@FreeBSD.org Cc: freebsd-stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: NFS/TCP Message-ID: <20060929172953.GC31887@xor.obsecurity.org> In-Reply-To: <451CD4DA.8060906@irfu.se> References: <200605081354.58807.yuri@irfu.se> <20060508174133.GA48163@xor.obsecurity.org> <200605111111.07882.yuri@irfu.se> <451CD4DA.8060906@irfu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
--lCAWRPmW1mITcIfM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I don't know if mohan already committed it, so perhaps he can comment. Kris On Fri, Sep 29, 2006 at 10:10:02AM +0200, Yuri Khotyaintsev wrote: > Will a fix for NFS/TCP (nfs_socket.c rev 1.138) be ever committed to stab= le? >=20 > Yuri Khotyaintsev wrote: > >On Monday 08 May 2006 19:41, Kris Kennaway wrote: > > =20 > >>On Mon, May 08, 2006 at 01:54:58PM +0200, Yuri Khotyaintsev wrote: > >> =20 > >>>I have an NSF server and several clients which write large text files = to > >>>the server. All machines are running max one week old STABLE and are > >>>connected to the same gigabit switch, and have identical nics (em). Amd > >>>mount options are: /defaults > >>>type:=3Dnfs;cache:=3Dall;opts:=3Drw,intr,nosuid,grpid,nfsv3,tcp,resvpo= rt,soft > >>> > >>>Almost all the time I get the following messages on the server: > >>> > >>>nfsd send error 32 > >>>nfsd send error 32 > >>>nfsd send error 32 > >>>nfsd send error 32 > >>>nfsd send error 32 > >>>... > >>> > >>>And corresponding messages on a client: > >>> > >>>impossible packet length (8996061) from nfs server db:/export/data1/caa > >>>impossible packet length (3123011) from nfs server db:/export/data1/caa > >>>impossible packet length (893006905) from nfs server db:/export/data1/= caa > >>>impossible packet length (842018868) from nfs server db:/export/data1/= caa > >>>impossible packet length (874220) from nfs server db:/export/data1/caa > >>>impossible packet length (14182767) from nfs server db:/export/data1/c= aa > >>>impossible packet length (16777216) from nfs server db:/export/data1/c= aa > >>>impossible packet length (758134573) from nfs server db:/export/data1/= caa > >>>impossible packet length (1503661568) from nfs server > >>>db:/export/data1/caa impossible packet length (1300840) from nfs server > >>>db:/export/data1/caa ... > >>> > >>>And from time to time the files which are written to the server get > >>>truncated (regardless of the file size)... > >>> > >>>Does anybody have an idea how to make it work reliably and not to > >>>truncate the files? > >>> =20 > >>mohan committed a fix for one such problem a few days ago. It will > >>not be in 6.1-RELEASE, but you should be able to apply the patch > >>yourself. It would be nice to know how it works for you. > >> > >>=20 > >>http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/nfsclient/nfs_socket.c.di= ff?r > >>1=3Dtext&tr1=3D1.136&r2=3Dtext&tr2=3D1.139 > >> =20 > > > >I have patched nfs_socket.c on all clients and run the same kind of=20 > >processing which was causing the problem. I can report that the problem = is=20 > >gone with nfs_socket.c rev 1.139. I only got one "nfs send error 35" on= =20 > >one of the clients instead of hundreds of messages I was seeing before.= =20 > >Thank you very much! > > =20 > --=20 > Dr. Yuri Khotyaintsev > Institutet f??r rymdfysik (IRF), Uppsala >=20 >=20 --lCAWRPmW1mITcIfM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFHVgRWry0BWjoQKURAinRAKDwWRQEhU+zxUVCqIhldLNPumiYVQCg3DdR gybsZiag71fr14UmX9eReTQ= =mp1Q -----END PGP SIGNATURE----- --lCAWRPmW1mITcIfM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060929172953.GC31887>