From owner-freebsd-stable@FreeBSD.ORG Sun Oct 1 01:42:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 140F816A40F for ; Sun, 1 Oct 2006 01:42:04 +0000 (UTC) (envelope-from mohan_srinivasan@yahoo.com) Received: from web30806.mail.mud.yahoo.com (web30806.mail.mud.yahoo.com [68.142.200.149]) by mx1.FreeBSD.org (Postfix) with SMTP id 6071243D49 for ; Sun, 1 Oct 2006 01:42:03 +0000 (GMT) (envelope-from mohan_srinivasan@yahoo.com) Received: (qmail 52106 invoked by uid 60001); 1 Oct 2006 01:42:02 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=tHhqvHLTIQ4mxxiLYLOk9bhutFFqLxDFxzvZJrajrslC6jbpdnkZp1NF99KDaiO6P2NPuXMHxmhqDXWyfNVQw4S7NyoqVqwGVPx28oCVTLrA8IoQw+X4+1EsMePaZZ8vxhEKKKYmvqEw9fJaZ94WPU2O2mVOUsD0tsfD202CpMo= ; Message-ID: <20061001014202.52104.qmail@web30806.mail.mud.yahoo.com> Received: from [71.139.37.164] by web30806.mail.mud.yahoo.com via HTTP; Sat, 30 Sep 2006 18:42:02 PDT Date: Sat, 30 Sep 2006 18:42:02 -0700 (PDT) From: Mohan Srinivasan To: Kris Kennaway , Yuri Khotyaintsev , mohans@FreeBSD.org In-Reply-To: <20060929172953.GC31887@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: re@freensd.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: NFS/TCP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2006 01:42:04 -0000 I thought I had MFC'ed the fix to releng_6. Maybe I did not :(. Sorry... I don't know if it is too late to get this into 6.1 or not. cc:ing re: for his comments. This is a pretty serious bug, and if there are last minute fixes being accepted, I would like this to go in. Unfortunately, cvs.freebsd.org seems to have changed from what I was familiar with. Now that website displays some perforce nonsense, which I can't grok. I am trying to see if there's a link someplace where I can see cvs comments. mohan --- Kris Kennaway wrote: > 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 stable? > > > > Yuri Khotyaintsev wrote: > > >On Monday 08 May 2006 19:41, Kris Kennaway wrote: > > > > > >>On Mon, May 08, 2006 at 01:54:58PM +0200, Yuri Khotyaintsev wrote: > > >> > > >>>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:=nfs;cache:=all;opts:=rw,intr,nosuid,grpid,nfsv3,tcp,resvport,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/caa > > >>>impossible packet length (16777216) from nfs server db:/export/data1/caa > > >>>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? > > >>> > > >>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. > > >> > > >> > > >>http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/nfsclient/nfs_socket.c.diff?r > > >>1=text&tr1=1.136&r2=text&tr2=1.139 > > >> > > > > > >I have patched nfs_socket.c on all clients and run the same kind of > > >processing which was causing the problem. I can report that the problem is > > >gone with nfs_socket.c rev 1.139. I only got one "nfs send error 35" on > > >one of the clients instead of hundreds of messages I was seeing before. > > >Thank you very much! > > > > > -- > > Dr. Yuri Khotyaintsev > > Institutet f??r rymdfysik (IRF), Uppsala > > > > >