All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David B. Ritch" <dritch@hpti.com>
To: Nicolas Brainez <nb@many.be>
Cc: nfs@lists.sourceforge.net
Subject: Re: Performance problem
Date: 13 May 2002 12:35:24 -0400	[thread overview]
Message-ID: <1021307724.2651.3.camel@twitch> (raw)
In-Reply-To: <1021302616.27660.20.camel@nb>

Make sure that your server and clients agree on the MTU of the network. 
I don't recall having seen the request slot message associated with that
sort of problem, but an MTU problem can cause messages to be dropped.

Can you nfs-mount a partition exported from the server on the server
itself?  If so, can you copy on the nfs-mounted partition?  (Trying to
isolate the issue from the network)

David Ritch

On Mon, 2002-05-13 at 11:10, Nicolas Brainez wrote:
> Hello,
> 
> I have an nfs server who exports some backup directories for the lan's
> users, it's a new install.
> 
> First I would like say that's not an hardware problem, because we have
> no problem to use appletalk, ftp, ...
> 
> I can mount remotly a partition on the nfs server without problem but
> when I copy something on it, the client ('cp' in this case) hangs, and I
> receive these messages on my console :
> 
> nfs: task XXX can't get a request slot
> 
> where XXX is begin from 1 to...
> 
> When I look on the server, the file I was trying to copy is only 8192
> bytes :
> 
> -rwxr-xr-x    1 root     root         8192 May 13 16:56 bash
> 
> After looking web, newsgroup, etc.. I've tried all what I can do to
> optimize performance (wsize=8192,rsize=8192,hard/soft, etc.. etc..)
> 
> The only changes is when I use wsize and rsize to 8192, the file I sent
> to the server can goes to 16384 bytes, but never more..
> 
> This is a LAN of ~ 10 computers, 100mbps, and we use switchs.
> The servers and workstation use Debian woody, nfs kernel and user server
> tried, same results.
> 
> Any type of help is welcome.
> 
> Thanks.
> 
> --
> Nicolas Brainez
> 
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2002-05-13 16:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13 15:10 Performance problem Nicolas Brainez
2002-05-13 15:17 ` Trond Myklebust
2002-05-13 15:34   ` Nicolas Brainez
2002-05-14  6:41     ` Trond Myklebust
2002-05-13 16:35 ` David B. Ritch [this message]
2002-05-13 16:48   ` Greg Lindahl
     [not found] <62D26CC4CB1CD3118EAA00805FBB65FA0B8B905E@perm01.woodside.com.au>
2002-05-15  8:46 ` Nicolas Brainez
2002-05-15 17:42   ` Greg Lindahl
  -- strict thread matches above, loose matches on Subject: below --
2002-04-22 13:33 Gregor Pavlin
2002-04-22 14:23 ` Joseph Bueno

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=1021307724.2651.3.camel@twitch \
    --to=dritch@hpti.com \
    --cc=nb@many.be \
    --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.