From: Greg Banks <gnb@sgi.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: ETIMEDOUT in nfsd?
Date: Tue, 3 Aug 2004 18:15:03 +1000 [thread overview]
Message-ID: <20040803081503.GM5581@sgi.com> (raw)
G'day,
I'm looking at porting to 2.6 the SGI ProPack code for supporting
Hierarchical Storage Managers in nfsd. Basically, this comprises
telling the filesystem to do stuff non-blocking at various times
(read, write and setattr) and converting the resulting -EAGAIN
when the HSM has to go out to tape into NFSERR_JUKEBOX to the
client.
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?
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
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
next reply other threads:[~2004-08-03 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 8:15 Greg Banks [this message]
2004-08-03 19:16 ` ETIMEDOUT in nfsd? J. Bruce Fields
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=20040803081503.GM5581@sgi.com \
--to=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.