From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
David Noveck <david.noveck@emc.com>
Subject: Re: NFS: Treat NFS4ERR_CLID_INUSE as a fatal error
Date: Fri, 10 Aug 2012 16:53:05 -0400 [thread overview]
Message-ID: <20120810205305.GD17985@fieldses.org> (raw)
In-Reply-To: <20120810203930.GC17985@fieldses.org>
On Fri, Aug 10, 2012 at 04:39:30PM -0400, J. Bruce Fields wrote:
> On Fri, Aug 10, 2012 at 04:33:46PM -0400, Chuck Lever wrote:
> > OK, I didn't notice that you were unmounting between the tests. 3.5 and before did update the boot verifier after the last mount of a server goes away, but that's also not desirable behavior. So I guess 3.6 also has my patch which makes the NFS client use the same boot verifier until it reboots, as God and the authors of 3530 intended?
>
> I don't know. (Why is that the right thing to do? Telling the server
> when you're not using the client any more seems reasonable to me.)
And anyway can't the trick described in
2c820d9a97f07b273b2c8a5960bd52b1b5864c68 "NFS: Force server to
drop NFSv4 state"
be used to do that without changing the boot verifier?
--b.
next prev parent reply other threads:[~2012-08-10 20:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 18:35 NFS: Treat NFS4ERR_CLID_INUSE as a fatal error J. Bruce Fields
2012-08-09 19:06 ` Chuck Lever
2012-08-09 19:37 ` J. Bruce Fields
2012-08-09 20:38 ` J. Bruce Fields
2012-08-09 20:46 ` Chuck Lever
2012-08-09 20:52 ` Chuck Lever
2012-08-09 21:13 ` J. Bruce Fields
2012-08-09 21:29 ` Chuck Lever
2012-08-09 21:38 ` J. Bruce Fields
2012-08-10 19:38 ` Chuck Lever
2012-08-10 20:13 ` J. Bruce Fields
2012-08-10 20:33 ` Chuck Lever
2012-08-10 20:39 ` J. Bruce Fields
2012-08-10 20:53 ` J. Bruce Fields [this message]
2012-08-10 21:22 ` Chuck Lever
2012-08-21 18:24 ` J. Bruce Fields
2012-08-21 18:57 ` Chuck Lever
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=20120810205305.GD17985@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=david.noveck@emc.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