>Not sure. Is there a way that the server can say, "I got your request,
>but I'm too busy now, try again in a little bit." ??
Isn't this what NFSERR_JUKEBOX is for?
AFAIK, the protocol goes something like this:
Client sends a request.
Server starts loading tape/optical disk/whatever.
Client resends request.
Server notices that this is a repeat of an earlier request which is already
in the "slow queue", and replies NFSERR_JUKEBOX (= "be patient, I'll send
the response eventually").
Client shuts up and waits.
Server completes request and sends response to client.
It seems that what the linux client is doing is returning error 528
to the user program (cp is giving this error message). From
linux/errno.h:
#define EJUKEBOX 528 /* Request initiated, but will not complete
before timeout */
This is wrong because the nfs file system is hard mounted in my case
- there is no timeout.
While it would be nice to do a perfect solution, it looks like
a quick fix is to just ignore NFSERR_JUKEBOX from the server.
Bob Smart
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/