All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>,
	Pankaj Singh <psingh.ait@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: When can nfsv3 returns nfs3err_jukebox to client?
Date: Wed, 06 Jul 2016 09:26:35 -0400	[thread overview]
Message-ID: <1467811595.3622.2.camel@redhat.com> (raw)
In-Reply-To: <1841001989.22448255.1467799567282.JavaMail.zimbra@desy.de>

On Wed, 2016-07-06 at 12:06 +0200, Mkrtchyan, Tigran wrote:
> Hi,
> 
> ----- Original Message -----
> > 
> > From: "Pankaj Singh" <psingh.ait@gmail.com>
> > To: linux-nfs@vger.kernel.org
> > Sent: Wednesday, July 6, 2016 7:52:45 AM
> > Subject: When can nfsv3 returns nfs3err_jukebox to client?
> > 
> > Hi All,
> > 
> > I have read in the RFC 1813 that "nfs3err_jukebox" will be return only
> > when server is not able to finish the RPC request within time. To
> > indicate client to wait and retry again.
> > 
> > Could anyone tell me is there any senario where NFSv3 or SUN RPC can
> > send this error to client, if not returned from base filesystem?
> > 
> If a migrating file system exported through NFS, then server may return
> err_jukebox/delay to the client on an IO request while mounting the offline
> volume or tape to make it accessible.
> 
> Tigran.
> 

I think that was the original intent, but many servers will return that
whenever there is a problem that is perceived as temporary. For
instance, knfsd will often return that when it hits a problem
allocating memory while processing an RPC.

-- 
Jeff Layton <jlayton@redhat.com>


      reply	other threads:[~2016-07-06 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  5:52 When can nfsv3 returns nfs3err_jukebox to client? Pankaj Singh
2016-07-06 10:06 ` Mkrtchyan, Tigran
2016-07-06 13:26   ` Jeff Layton [this message]

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=1467811595.3622.2.camel@redhat.com \
    --to=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=psingh.ait@gmail.com \
    --cc=tigran.mkrtchyan@desy.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 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.