From: Malahal Naineni <malahal@us.ibm.com>
To: linux-nfs@vger.kernel.org
Subject: Re: State of NFSv4 VolatileFilehandles
Date: Wed, 3 Aug 2011 08:43:03 -0700 [thread overview]
Message-ID: <20110803154303.GA11165@us.ibm.com> (raw)
In-Reply-To: <4E38F894.4070003@linux.vnet.ibm.com>
Venkateswararao Jujjuri [jvrao@linux.vnet.ibm.com] wrote:
> >I think we are avoiding volatile file handles as long as possible. We don't have plans to implement them at the moment.
> Hrm. How can we achieve the complete migration support without
> volatile filehandle support?
If you can generate persistent file handles that don't include server
specific information (maybe a bit hard, but not impossible), migration
can be done. Maybe that is what Chuck is talking about.
next prev parent reply other threads:[~2011-08-03 15:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 11:58 State of NFSv4 VolatileFilehandles Venkateswararao Jujjuri
2011-08-02 14:53 ` Chuck Lever
2011-08-03 7:28 ` Venkateswararao Jujjuri
2011-08-03 12:27 ` Myklebust, Trond
2011-08-03 22:23 ` NeilBrown
2011-08-04 1:16 ` Malahal Naineni
2011-08-04 2:12 ` Trond Myklebust
2011-08-15 20:49 ` Malahal Naineni
2011-08-16 8:06 ` Trond Myklebust
2011-08-16 15:59 ` Malahal Naineni
2011-08-16 22:24 ` NeilBrown
2011-08-03 15:43 ` Malahal Naineni [this message]
2011-08-03 22:13 ` Chuck Lever
2011-08-04 11:27 ` Venkateswararao Jujjuri
2011-08-04 16:03 ` J. Bruce Fields
2011-08-04 16:10 ` Trond Myklebust
2011-08-04 16:27 ` J. Bruce Fields
2011-08-04 16:48 ` Myklebust, Trond
2011-08-04 17:03 ` J. Bruce Fields
2011-08-04 17:21 ` Trond Myklebust
2011-08-04 17:30 ` J. Bruce Fields
2011-08-04 17:38 ` Trond Myklebust
2011-08-05 13:38 ` Christoph Hellwig
2011-08-05 19:16 ` J. Bruce Fields
2011-08-10 10:24 ` Christoph Hellwig
2011-08-04 15:56 ` J. Bruce Fields
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=20110803154303.GA11165@us.ibm.com \
--to=malahal@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.