[lkml]   [2009]   [Jul]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 16/20] ceph: nfs re-export support
On Thu, 16 Jul 2009, Trond Myklebust wrote:
> On Thu, 2009-07-16 at 12:50 -0700, Sage Weil wrote:
> > On Thu, 16 Jul 2009, J. Bruce Fields wrote:
> > > On Wed, Jul 15, 2009 at 02:24:46PM -0700, Sage Weil wrote:
> > > > Basic NFS re-export support is included. This mostly works. However,
> > > > Ceph's MDS design precludes the ability to generate a (small)
> > > > filehandle that will be valid forever, so this is of limited utility.
> > >
> > > Is there any hope of fixing that?
> >
> > Yes, but it requires some additional ondisk metadata the MDS isn't
> > maintaining yet (a parent directory backpointer on file objects).
> >
> > The MDS changes will mean more random IO for rename intensive workloads,
> > but the backpointers would also be useful for rebuilding the directory
> > tree in the event of some catastrophic metadata loss or corruption.
> > (Currently they're only there for directories, not all files.)
> Note that a filehandle that contains parent directory information is
> still not one that is valid forever. It will change in the case of a
> cross-directory rename, and so isn't a filehandle in the NFSv2/v3 sense.
> Even in the NFSv4 case, it would have to be labelled as 'volatile'.

Right. The parent directory information in the fh it used as a hint, but
can't be relied on because of the rename problem. That's exactly why the
Ceph MDS will need to be changed to maintain backpointers on all files,
not just directories. When that happens, reexporting via NFS will work
reliably. Until then, old and idle filehandles for renamed files will
eventually go stale.


 \ /
  Last update: 2009-07-17 00:09    [W:0.095 / U:1.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site