From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
NeilBrown <neilb@suse.de>,
Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>,
Christoph Hellwig <hch@infradead.org>,
Matthew Treinish <treinish@linux.vnet.ibm.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH/RFC 0/7] Volatile Filehandle Client-side Support
Date: Fri, 13 Jan 2012 20:38:34 -0500 [thread overview]
Message-ID: <20120114013834.GA20464@fieldses.org> (raw)
In-Reply-To: <20120113170914.GA31414@us.ibm.com>
On Fri, Jan 13, 2012 at 11:09:14AM -0600, Malahal Naineni wrote:
> Trond Myklebust [Trond.Myklebust@netapp.com] wrote:
> > On Mon, 2011-11-14 at 08:07 +1100, NeilBrown wrote:
> >
> > > If a server has objects that are never renamed, it can easily use volatile
> > > file handles.
> > > If a server has objects which can be renamed and wants to use volatile file
> > > handles, then if such an object is open and is about to be renamed, it must
> > > first log to stable storage some mapping to allow it to access the file from
> > > the old volatile file handle. And of course it cannot allow renames during
> > > the grace period, but I think we already have that.
> > > Also, if the VFH is such that it will be lost on a reboot, the server must
> > > log it to stable storage before allowing an open.
> >
> > BTW: If the namespace is stable, then the server can easily implement
> > permanent filehandles. Use a hash of the pathname as the filehandle, and
> > set up a hidden directory ('/.filehandles') containing symlinks that map
> > said hash back to the correct pathname. No need for volatile
> > filehandles.
>
> Neil and Trond, one of our use cases is for a read only file system. The
> name space is stable and Volatile File Handle support should not have
> any issues under those conditions, correct?
Dumb question: remind me which filesystem your exporting that can't
already generate stable filehandles?
--b.
>
> Trond, trying to understand how we can make file handles permanent at
> the servers with your ideas. We do use linux NFS server. Looks like the
> server needs a new config parameter to hide '/.filehandles' and use it
> for storing permanent file handles. Also, the solution needs a tool
> that generates/populates './filehandles' directory. I don't know how
> best we should handle hash collisions at this point (shouldn't be an
> issue once we agree to a method though). Anything else I am missing?
>
> Any thoughts from linux NFS server community? Is this approach
> acceptable?
>
> Regards, Malahal.
>
next prev parent reply other threads:[~2012-01-14 1:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 23:04 [PATCH/RFC 0/7] Volatile Filehandle Client-side Support Matthew Treinish
2011-11-11 23:04 ` [PATCH/RFC 1/7] New mount option for volatile filehandle recovery Matthew Treinish
2011-11-12 0:19 ` Trond Myklebust
2011-11-12 3:35 ` Malahal Naineni
2011-11-11 23:04 ` [PATCH/RFC 2/7] Added support for FH_EXPIRE_TYPE attribute Matthew Treinish
2011-11-11 23:04 ` [PATCH/RFC 3/7] Add VFS objects from nfs4_proc calls into nfs4_exception Matthew Treinish
2011-11-11 23:04 ` [PATCH/RFC 4/7] Save root file handle in nfs_server Matthew Treinish
2011-11-11 23:04 ` [PATCH/RFC 5/7] Added VFH FHEXPIRED recovery functions Matthew Treinish
2011-11-12 0:27 ` Trond Myklebust
2011-11-12 3:45 ` Malahal Naineni
2011-11-12 17:16 ` Trond Myklebust
2011-11-14 21:12 ` Matthew Treinish
2011-11-11 23:04 ` [PATCH/RFC 6/7] Perform recovery on both inodes for rename Matthew Treinish
2011-11-11 23:04 ` [PATCH/RFC 7/7] Added error handling for NFS4ERR_FHEXPIRED Matthew Treinish
2011-11-11 23:04 ` [PATCH/RFC] Hard code testing on server <ONLY FOR TESTING> Matthew Treinish
2011-11-12 0:13 ` [PATCH/RFC 0/7] Volatile Filehandle Client-side Support Trond Myklebust
2011-11-12 14:49 ` Christoph Hellwig
2011-11-13 3:54 ` NeilBrown
2011-11-13 13:45 ` Tigran Mkrtchyan
2011-11-13 16:36 ` J. Bruce Fields
2011-11-13 21:07 ` NeilBrown
2011-11-14 0:42 ` J. Bruce Fields
2011-11-14 1:26 ` NeilBrown
2011-11-14 17:27 ` Trond Myklebust
2011-11-15 6:33 ` Trond Myklebust
2012-01-13 17:09 ` Malahal Naineni
2012-01-14 1:38 ` J. Bruce Fields [this message]
2012-01-16 16:52 ` Malahal Naineni
2012-01-17 15:18 ` J. Bruce Fields
2012-01-17 17:22 ` Malahal Naineni
2012-01-17 18:47 ` J. Bruce Fields
2012-01-17 19:43 ` Malahal Naineni
2011-11-14 16:29 ` Trond Myklebust
2011-11-13 16:42 ` J. Bruce Fields
2011-11-13 16:45 ` J. Bruce Fields
2011-11-13 18:25 ` Matthew Treinish
2011-11-13 18:06 ` Matthew Treinish
2011-11-14 9:09 ` Tigran Mkrtchyan
2011-11-14 21:47 ` Matthew Treinish
2011-11-15 6:49 ` Trond Myklebust
2011-11-15 22:38 ` Matthew Treinish
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=20120114013834.GA20464@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tigran.mkrtchyan@desy.de \
--cc=treinish@linux.vnet.ibm.com \
/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