From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: "Adamson, Andy" <William.Adamson@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH Version 3 1/1] NFSv4 wait on recovery for async session errors
Date: Tue, 19 Nov 2013 22:47:12 +0000 [thread overview]
Message-ID: <1384901232.45997.4.camel@leira.trondhjem.org> (raw)
In-Reply-To: <C662575C-1FBD-4E72-B569-0BD4FC6BFE47@netapp.com>
On Tue, 2013-11-19 at 22:43 +0000, Adamson, Andy wrote:
> Why not recover the lease? Shouldn't NFS4ERR_EXPIRED be left for the async handler?
No, because then it will retry the operation. Since it is impossible to
recover the delegation at this point, then that will result in another
failure.
> -->Andy
>
> On Nov 19, 2013, at 5:34 PM, "Myklebust, Trond" <Trond.Myklebust@netapp.com>
> wrote:
>
> > On Tue, 2013-11-19 at 16:49 -0500, Trond Myklebust wrote:
> >> There is a second patch that goes with this problem. Please see the
> >> following attachment.
> >
> > V2: Don't return an error when we know that the stateid is no longer
> > valid.
> >
> > --
> > Trond Myklebust
> > Linux NFS client maintainer
> >
> > NetApp
> > Trond.Myklebust@netapp.com
> > www.netapp.com
> > <0001-NFSv4-Update-list-of-irrecoverable-errors-on-DELEGRE.patch>
>
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2013-11-19 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 21:36 [PATCH Version 3 1/1] NFSv4 wait on recovery for async session errors andros
2013-11-19 21:49 ` Myklebust, Trond
2013-11-19 22:34 ` Myklebust, Trond
2013-11-19 22:43 ` Adamson, Andy
2013-11-19 22:47 ` Myklebust, Trond [this message]
2013-11-20 9:29 ` William Dauchy
2013-11-21 23:48 ` William Dauchy
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=1384901232.45997.4.camel@leira.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=William.Adamson@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).