Linux NFS development
 help / color / mirror / Atom feed
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
To: Simon Peter <simon.peter@gmx.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: Delays on "first" access to a NFS mount
Date: Wed, 07 Mar 2007 07:38:09 -0500	[thread overview]
Message-ID: <EXNANE015HfqR77bieL0000006b@exnane01.hq.netapp.com> (raw)
In-Reply-To: <20070307112347.6a40faff.simon.peter@gmx.de>

The delay seems to be on the server side. What is the server running?
Does it have any nameservice issues? Delays on the first response can
often be due to server exports checking, which usually requires reverse
name lookups.

Tom.

At 05:23 AM 3/7/2007, Simon Peter wrote:
>Hi,
>
>I get a good 10 second delay anytime I am accessing my NFS mounts from
>a client for the first time (or after a long time not accessing them --
>I suppose whenever the cache is cleared or something similar).
>
>I usually did not bother, even though it is very annoying, but this
>time I collected a network protocol capture, which is attached. Notice
>the big delay between packet #6 and #8, while #7 should show that it is
>not a network issue.
>
>I would be very glad if somebody could explain these delays.
>
>Thanks,
>Simon


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-03-07 12:38 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 10:23 Delays on "first" access to a NFS mount Simon Peter
2007-03-07 12:38 ` Talpey, Thomas [this message]
2007-03-07 13:22   ` Simon Peter
2007-03-07 15:06   ` Simon Peter
2007-03-07 15:10     ` Simon Peter
2007-03-07 15:42     ` J. Bruce Fields
2007-03-07 18:44       ` Simon Peter
2007-03-07 20:29         ` J. Bruce Fields
2007-03-07 21:46           ` Simon Peter
2007-03-07 22:05             ` J. Bruce Fields
2007-03-07 23:19               ` Simon Peter
2007-03-07 22:09           ` Neil Brown
2007-03-08 15:49           ` Simon Peter
2007-03-09 13:02           ` Simon Peter
2007-03-09 14:59             ` J. Bruce Fields
2007-03-07 20:31         ` Talpey, Thomas
2007-03-07 20:50           ` J. Bruce Fields
2007-03-07 21:07             ` Talpey, Thomas
2007-03-07 21:17               ` J. Bruce Fields
2007-03-07 21:23                 ` Talpey, Thomas
2007-03-07 21:54                   ` J. Bruce Fields
2007-03-07 22:37                     ` Neil Brown
2007-03-07 23:06                       ` J. Bruce Fields
2007-03-07 23:39                         ` Neil Brown
2007-03-08  5:14                           ` J. Bruce Fields
2007-03-08  5:42                             ` Neil Brown
2007-03-08 13:43                             ` Olaf Kirch
2007-03-08 21:27                               ` J. Bruce Fields
2007-03-09 15:02                                 ` Olaf Kirch
2007-03-16 21:47                         ` Christoph Hellwig
2007-03-16 21:54                           ` J. Bruce Fields
2007-03-16 21:57                             ` Christoph Hellwig
2007-03-07 23:24                       ` J. Bruce Fields
2007-03-07 23:51                         ` Neil Brown
2007-03-08  4:36                           ` J. Bruce Fields
2007-03-08 13:27                     ` Olaf Kirch
2007-03-08 21:46                       ` J. Bruce Fields
2007-03-07 22:15                   ` Neil Brown
2007-03-07 21:40             ` Simon Peter
2007-03-07 22:17               ` Neil Brown
2007-03-07 22:36                 ` Talpey, Thomas
2007-03-07 22:48                   ` Neil Brown
2007-03-07 22:56                     ` Talpey, Thomas
2007-03-07 22:12             ` Neil Brown
2007-03-07 22:23               ` J. Bruce Fields

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=EXNANE015HfqR77bieL0000006b@exnane01.hq.netapp.com \
    --to=thomas.talpey@netapp.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=simon.peter@gmx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox