All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Blandford <mlblandf@sedona.ch.intel.com>
To: jmoyer@redhat.com
Cc: autofs@linux.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: [RFC] rpc_ping and looong timeouts
Date: Tue, 08 Jun 2004 09:09:04 -0700	[thread overview]
Message-ID: <40C5E4A0.10405@sedona.intel.com> (raw)
In-Reply-To: <16580.46990.794712.901678@segfault.boston.redhat.com>

Jeff Moyer wrote:

>mlblandf> Would this patch cause problems for those of us who have icmp
>mlblandf> blocked?  If so, could we make it a run time option to
>mlblandf> enable/disable?
>
>Wow, you block icmp internally?  This would incur a timeout for every host
>listed in your replicated server entry, and with Ian's patch, it would
>incur a timeout for non-replicated servers, as well.  In fact, for the
>non-replicated server case, I think it would give a false negative, failing
>the mount even though the server is up.
>
>Is this really how you have things configured?  NFS clients can't ping
>their servers?
>  
>

In a large environment it wouldn't be uncommon to have NFS mounts that 
span across a WAN.  Using NFS over TCP seems to make the most sense in 
that situation.

As packets traverse the WAN, there may be routers that block icmp.  This 
is the type of situation where replicated server would make the most 
sense - find the fastest server.


Michael

Disclaimer: The content of this message is my personal opinion only and 
although I am an employee of Intel, the statements I make here in no way 
represent Intel's position on the issue, nor am I authorized to speak on 
behalf of Intel on this matter.

  reply	other threads:[~2004-06-08 16:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 20:30 [RFC] rpc_ping and looong timeouts Jeff Moyer
2004-06-04  1:17 ` Ian Kent
2004-06-04 19:06   ` Jeff Moyer
2004-06-04 21:41     ` Jeff Moyer
2004-06-05  2:08       ` raven
2004-06-06  2:18         ` Jeff Moyer
2004-06-05  5:36       ` raven
2004-06-06  3:00         ` Jeff Moyer
2004-06-06  3:13           ` raven
2004-06-06  3:57             ` Jeff Moyer
2004-06-07 18:29       ` Michael Blandford
2004-06-07 18:44         ` Jeff Moyer
2004-06-08 16:09           ` Michael Blandford [this message]
2004-06-08 16:15             ` raven
2004-06-08 16:26               ` Jeff Moyer
2004-06-08 16:36                 ` raven
2004-06-08 17:25                   ` Jeff Moyer
2004-06-08 17:51                     ` Michael Blandford
2004-06-09  1:13                     ` Ian Kent
2004-06-09  2:22                       ` Jeff Moyer
2004-06-09  2:54                         ` Ian Kent
2004-06-08  0:56         ` Ian Kent
2004-06-08  3:17           ` Peter C. Norton
2004-06-05  1:58     ` raven

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=40C5E4A0.10405@sedona.intel.com \
    --to=mlblandf@sedona.ch.intel.com \
    --cc=autofs@linux.kernel.org \
    --cc=jmoyer@redhat.com \
    --cc=raven@themaw.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.