From: Danny Smith <dannys@cinesite.co.uk>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs <nfs@lists.sourceforge.net>, Iain Irwin-Powell <Iain@cinesite.co.uk>
Subject: Re: NFSERR_EAGAIN
Date: Fri, 11 Jul 2003 10:55:01 +0100 [thread overview]
Message-ID: <3F0E8975.2000009@cinesite.co.uk> (raw)
In-Reply-To: <shsbrw20zue.fsf@charged.uio.no>
Trond Myklebust wrote:
>>>>>>" " == Danny Smith <dannys@cinesite.co.uk> writes:
>>>>>>
>>>>>>
>
> > Looking through nfs2xdr.c and nfs.h and googling, it seems that
> > error number 11 is not properly defined, but certainly seems to
> > be in use by SGI. From nfs2xdr.c:
>
> > { NFSERR_NXIO, ENXIO },
>
> > /* { NFSERR_EAGAIN, EAGAIN }, */
> > { NFSERR_ACCES, EACCES },
>
> > (EAGAIN having value 11)
>
> > Does anyone know much about the history of this? Was this
> > removed in order to be RFC compliant, or is there a stronger
> > motivation not to have this?
>
>Why should we be supporting something which isn't documented in the RFCs?
>
I really want to know how it got into the source in the first place? Is
it a feature that's "not part of the standard, but seem to be widely
used nevertheless" (quoting from nfs.h).
Searching around shows a (very) few ocurrences of this, with Solaris and
IRIX servers, although often accompanied by other issues.
If the server is broken, but we can work with it anyway without
upsetting anything else, this would be a "good thing" in my book (of
course, we would take it up with SGI too).
>What is this error anyway? Is it some SGI hack for emulating
>NFS3ERR_JUKEBOX under NFSv2?
>
>
Right now, I don't really know, but I'm guessing it's something of the
sort (seems to make sense with what we're seeing).
I'm trying to get a packet trace to verify this is indeed what is being
sent - will update when I have further evidence.
Danny
--
Danny Smith
Senior Systems Administrator, Cinesite (Europe) Ltd
020 7973 4000 - x4055 / dannys@cinesite.co.uk
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-07-11 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 18:29 NFSERR_EAGAIN Danny Smith
2003-07-10 22:41 ` NFSERR_EAGAIN Trond Myklebust
2003-07-11 9:55 ` Danny Smith [this message]
2003-07-11 10:13 ` NFSERR_EAGAIN Trond Myklebust
2003-07-16 15:53 ` NFSERR_EAGAIN - resolved Danny Smith
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=3F0E8975.2000009@cinesite.co.uk \
--to=dannys@cinesite.co.uk \
--cc=Iain@cinesite.co.uk \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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