All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Sebastiano <robs@multiplayer.it>
To: nfs@lists.sourceforge.net
Subject: gigabit, 2.4.22 and timeo
Date: Tue, 14 Oct 2003 14:24:31 +0200	[thread overview]
Message-ID: <1066134271.629.19.camel@newdeal> (raw)

Hi,
I have this hw setup:
1 Dual PIII 1Ghz, Intel PRO/1000MT nic, linux 2.4.22 (nfs client)
1 Single P4 2.53Ghz, Intel PRO/1000MT nic, linux 2.4.22, fast RAID5 scsi
disk subsystem (nfs server)
These are cross-connected and both have jumbo frames enabled
This setup will (hopefully) be used to share files between two web
servers under load balancing

Now, to the problem.
I specified the mount options as follows (from /proc/mounts):
rw,v3,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=192.168.2.1

When I copy a large file over the network, on the client side I see: 
Oct 14 13:39:24 flanders kernel: nfs: server 192.168.2.1 not responding,
still trying
Oct 14 13:39:24 flanders last message repeated 5 times
Oct 14 13:39:24 flanders kernel: nfs: server 192.168.2.1 OK
Oct 14 13:39:24 flanders last message repeated 5 times
Oct 14 13:39:25 flanders kernel: nfs: server 192.168.2.1 not responding,
still trying
Oct 14 13:39:26 flanders last message repeated 11 times
Oct 14 13:39:26 flanders kernel: nfs: server 192.168.2.1 OK

But the cp process goes just fine.
Setting retrans to 5 or higher "solves" the problem (copying is still ok
and no errors are triggered), but setting timeo to a larger value (60 or
so) doesn't seem to have any effect (between the start of the copy and
the printf of the message, there are only two seconds or so)

I think that the client is just assuming a too low timeout value, and it
keeps sending requests
I found that with nfs over TCP this problem doesn't occur


Is there any way to solve this ?

Thanks,
-- 
Roberto Sebastiano <robs@multiplayer.it>



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-10-14 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 12:24 Roberto Sebastiano [this message]
2003-10-14 14:39 ` gigabit, 2.4.22 and timeo Trond Myklebust
2003-10-14 16:21   ` Roberto Sebastiano
2003-10-14 16:26     ` Trond Myklebust
2003-10-14 17:02       ` Roberto Sebastiano
2003-10-14 18:31         ` Trond Myklebust

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1066134271.629.19.camel@newdeal \
    --to=robs@multiplayer.it \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.