All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Greg Banks <gnb@sgi.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
	Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: ETIMEDOUT in nfsd?
Date: Tue, 3 Aug 2004 15:16:10 -0400	[thread overview]
Message-ID: <20040803191610.GC7781@fieldses.org> (raw)
In-Reply-To: <20040803081503.GM5581@sgi.com>

On Tue, Aug 03, 2004 at 06:15:03PM +1000, Greg Banks wrote:
> So I was somewhat surprised to see that in 2.6, the mapping from
> Linux errno to NFS error in fs/nfsd/nfsproc.c:nfserrno() maps
> -EAGAIN to nfserr_dropit, causing nfsd_dispatch to just drop the
> call and not reply.  Furthermore I need to return the network
> error -ETIMEDOUT to get NFSERR_JUKEBOX.  I don't get it...can
> someone explain both of these?

The server does upcalls to userspace daemons (usually to mountd to get
export options or IP address->client name mappings) by doing a lookup in
a cache, and returning -EAGAIN if an upcall is required.  The request is
then dropped, a copy of the request is made (see svcsock.c:svc_defer())
and reprocessed at a later time (see svcsock.c:svc_revisit()).

I have some rough notes on all this at

http://www.fieldses.org/~bfields/kernel/svc_caches/sunrpc_svc_cache.txt

and Neil has some documentation in Documentation/sunrpc-cache.txt.

--Bruce Fields


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-08-03 19:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03  8:15 ETIMEDOUT in nfsd? Greg Banks
2004-08-03 19:16 ` J. Bruce Fields [this message]
2004-08-04  7:35   ` Greg Banks
2004-08-04 14:13     ` J. Bruce Fields
2004-08-05  2:26       ` Greg Banks
2004-08-05 14:21         ` J. Bruce Fields
2004-08-06  0:50           ` Greg Banks
2004-08-06 18:20             ` 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=20040803191610.GC7781@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=gnb@sgi.com \
    --cc=neilb@cse.unsw.edu.au \
    --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.