From owner-freebsd-stable Sun Jul 7 9:56:51 2002 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 70F8437B400 for ; Sun, 7 Jul 2002 09:56:47 -0700 (PDT) Received: from ns.wuppy.net.ru (ns.WUPPY.NET.RU [212.30.189.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 432A243E3B for ; Sun, 7 Jul 2002 09:56:45 -0700 (PDT) (envelope-from romanp@unshadow.net) Received: from room101.wuppy.net.ru (room101.WUPPY.NET.RU [212.30.189.131]) by ns.wuppy.net.ru (Postfix) with ESMTP id E10E01E03; Sun, 7 Jul 2002 20:56:38 +0400 (MSD) Date: Sun, 7 Jul 2002 20:56:38 +0400 (MSD) From: "Roman V. Palagin" To: John Polstra Cc: stable@FreeBSD.ORG Subject: Re: NFS errors at high hz values with TCP mounts In-Reply-To: <200207062254.g66MsJPj000565@vashon.polstra.com> Message-ID: <20020707205408.Y416-100000@room101.wuppy.net.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Jul 6, at 3:54pm -0700, John Polstra wrote: > > > Here's what happens when I try to copy a 512 kbyte file from the > > > hz=10000 client to a server that is NFS-mounted: > > > > > > thin$ dd if=/dev/zero of=/mnt/foo count=1000 > > > dd: /mnt/foo: Resource temporarily unavailable > > > 61+0 records in > > > 60+0 records out > > > 30720 bytes transferred in 0.000996 secs (30843571 bytes/sec) > > > > I forget to mention that this message appears in the dmesg output on > > the client machine: > > > > nfs send error 35 for server strings:/usr/home/jdp > > > > It comes from sys/nfs/nfs_socket.c line 499. > > Sorry for the extended conversation with myself. :-) I think I > found the bug. In nfs_connect() at line 300 of sys/nfs/nfs_socket.c > we have this code: > > so->so_rcv.sb_timeo = (5 * hz); > so->so_snd.sb_timeo = (5 * hz); > > But sb_timeo has type "short", which overflows when hz is 10000. > > This is in struct sockbuf. I don't think it would break binary > compatibility with existing 3rd party modules to change it to type > "long". Are there any contrary opinions? I see this problem with HZ=1000, overflow doesn't occured in this situation... May be problem lies somewhere else? - Roman --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message