All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Furlong <douglas.furlong@firebox.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS server not responding
Date: Thu, 27 Nov 2003 19:07:13 +0000	[thread overview]
Message-ID: <1069960032.4680.71.camel@wibbit.firebox.com> (raw)
In-Reply-To: <shsfzg93hag.fsf@charged.uio.no>

On Thu, 2003-11-27 at 16:30, Trond Myklebust wrote:
> >>>>> " " == Douglas Furlong <douglas.furlong@firebox.com> writes:
> 
>      > Good day all.  I am running in to excessive amounts of NFS
>      > errors as below.
> 
>      > kernel: nfs: server neon not responding, still trying kernel:
>      > nfs: server neon OK
> 
> Two suggestions:
> 
>  1) Bump the number of threads on the server. 32 is probably a bit
>     low.

I have upped this to 64 now. Is there a rule of thumb with regards to
the number of people connecting/amount of system resources?

>  2) The value retrans=3 used as the default by the Linux 'mount'
>     program is rather low compared to that used on other OSes. I
>     suggest you bump it to at least 5 on all your clients.

I have increased the retrans value to 10 now. This appears to have
resolved the problems to a greater extent.

What sort of things would be causing the client to have to re-transmit
so often?

Client rpc stats:
calls      retrans    authrefrsh
3431978    15968      0    

Those retrans numbers, as a percentage of the calls, does it seem
appropriate?

Thanks for the tips.

Doug



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-11-27 19:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 12:00 NFS server not responding Douglas Furlong
2003-11-27 16:30 ` Trond Myklebust
2003-11-27 19:07   ` Douglas Furlong [this message]
2003-11-27 20:02     ` Trond Myklebust
2003-11-28  8:46 ` Juergen Sauer
2003-11-28  9:37   ` Douglas Furlong
2003-11-28 10:11     ` Juergen Sauer
2003-11-28 10:48       ` Douglas Furlong
2003-11-28 12:28         ` Bogdan Costescu
2003-11-28 16:56           ` Trond Myklebust
2003-11-28 18:43             ` Bogdan Costescu
2003-12-02 14:37             ` Douglas Furlong
2003-12-02 15:37               ` Trond Myklebust
2003-12-04 17:17                 ` Steve Dickson
2003-12-04 17:37             ` Steve Dickson
2003-12-04 18:39               ` Trond Myklebust
2003-12-04 19:11                 ` Steve Dickson
2003-12-04 20:55                   ` seth vidal
2003-12-04 21:24                     ` Steve Dickson
2003-12-05  2:53                       ` Kyle Rose
2003-12-09 19:47                         ` Steve Dickson
2003-12-09 20:09                           ` Kyle Rose
2003-12-05 15:50                 ` Bogdan Costescu
2003-11-30 20:01           ` seth vidal
2003-12-01 10:58             ` Bogdan Costescu
2003-11-28 12:36       ` Bogdan Costescu
  -- strict thread matches above, loose matches on Subject: below --
2004-07-30 17:09 nfs " Pavel Bartusek
2009-05-16  0:57 nfs: " Jerome Walters

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=1069960032.4680.71.camel@wibbit.firebox.com \
    --to=douglas.furlong@firebox.com \
    --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.