All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Marc Eshel <eshel@us.ibm.com>
Cc: "Adam C. Emerson" <aemerson@linuxbox.com>,
	"J. Bruce Fields" <bfields@redhat.com>,
	linux-nfs@vger.kernel.org,
	Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: NFSv4.1 session
Date: Thu, 27 Jun 2013 15:41:09 -0400 (EDT)	[thread overview]
Message-ID: <606311159.195.1372362069589.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <1444224014.193.1372361256986.JavaMail.root@thunderbeast.private.linuxbox.com>

Hi,

Keeping this simple, the controlling section of RFC 5661 is 2.10.5 (trunking).

If CLIENT presents the same eia_clientowner in two EXCHANGE_ID invocations
to "the same NFSv4.1 server" over two connections of differing network
address, 2.10.5 actually states that the server MUST return the same
value for eir_serverowner.  By our choice of the same server owner, we are
consenting to clientid trunking.

It doesn't seem like anything stops one instance of Ganesha from presenting itself
as two or more completely distinct NFSv4.1 servers in response to connections of
differing address.  They could share the same server scope (e.g., filehandle namespaces),
but they CANNOT share the same server owner, and consequently, they can't share
any state.  (So we think it would confuse the client if we return CLID_INUSE
on the second EXCHANGE_ID.)

Matt and Adam

----- "Marc Eshel" <eshel@us.ibm.com> wrote:

> If it was not clear I am talking about the exchange id operation.
> Marc.
> 
> 
> 
> From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
> To: Marc Eshel/Almaden/IBM@IBMUS,
> Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>, "J. Bruce
> Fields" <bfields@redhat.com>, "Adam C. Emerson"
> <aemerson@linuxbox.com>, "Matt W. Benjamin" <matt@linuxbox.com>
> Date: 06/27/2013 11:09 AM
> Subject: Re: NFSv4.1 session
> 
> 
> 
> 
> On Thu, 2013-06-27 at 11:00 -0700, Marc Eshel wrote:
> > Hi Trond,
> >
> > I am not able to mount from Linux NFS client to the same Ganesha NFS
> > server using multiple IP address. The client was providing the same
> > client-id so the server was using the same session. I tried to
> return
> > NFS4ERR_CLID_INUSE on the second mount if the target IP is different
> > but the client still did not provide a different client-id like it
> > should. I am not trying to use trunking I what to have different
> > server instance for each IP address so I can move that IP between
> > nodes in the cluster. Any ideas how to accomplish it.
> >
> > Thanks, Marc.
> 
> I don't understand. The client is performing exactly as per design: it
> detects the fact that you are talking to the same server, and so it
> reuses the same client and session. This is the only sane semantic for
> a
> NFS client...
> 
> --
> Trond Myklebust
> Linux NFS client maintainer
> 
> NetApp
> Trond.Myklebust@netapp.com
> www.netapp.com

-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 

       reply	other threads:[~2013-06-27 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1444224014.193.1372361256986.JavaMail.root@thunderbeast.private.linuxbox.com>
2013-06-27 19:41 ` Matt W. Benjamin [this message]
2013-06-27 22:32   ` NFSv4.1 session Marc Eshel
     [not found] <OF8A324DEB.5C9C96EC-ON88257B97.0061DA51-88257B97.0062ED43@us.ibm.com>
2013-06-27 18:05 ` Myklebust, Trond
     [not found]   ` <OF72D7519C.7F46B89C-ON88257B97.0063EB30-88257B97.006422E1@us.ibm.com>
2013-06-27 18:42     ` Myklebust, Trond
2013-06-27 19:46       ` Chuck Lever
     [not found]         ` <OF786412D5.F9D839FF-ON88257B97.0077EB71-88257B97.0078C3A8@us.ibm.com>
2013-06-28 14:47           ` 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=606311159.195.1372362069589.JavaMail.root@thunderbeast.private.linuxbox.com \
    --to=matt@linuxbox.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=aemerson@linuxbox.com \
    --cc=bfields@redhat.com \
    --cc=eshel@us.ibm.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 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.