[Bugs] [Bug 1240190] New: do an explicit lookup on the inodes linked in readdirp

bugzilla at redhat.com bugzilla at redhat.com
Mon Jul 6 07:26:48 UTC 2015


            Bug ID: 1240190
           Summary: do an explicit lookup on the inodes linked in readdirp
           Product: GlusterFS
           Version: 3.7.2
         Component: libgfapi
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: rabhat at redhat.com
        QA Contact: sdharane at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    ndevos at redhat.com, sdharane at redhat.com
        Depends On: 1236009

+++ This bug was initially created as a clone of Bug #1236009 +++

Description of problem:

Like fuse, its better to do an explicit lookup on the inodes linked via
readdirp. Otherwise, post linkage directly fops will come and below xlators
such as AFR, DHT will not be able to do their house keeping activities for the
inode, which they would have done in lookup.

So do an explicit lookup on those inodes linked via readdirp, before proceeding
with the first fop on those inodes.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

--- Additional comment from Anand Avati on 2015-07-02 05:16:18 EDT ---

COMMIT: http://review.gluster.org/11236 committed in master by Niels de Vos
(ndevos at redhat.com) 
commit c1a8ae20bd055227921d199b952582eca4104f67
Author: Raghavendra Bhat <raghavendra at redhat.com>
Date:   Fri Jun 12 15:12:05 2015 +0530

    libgfapi: send explicit lookups on inodes linked in readdirp

    If the inode is linked via readdirp, then the consuners of gfapi which are
    handles (got either in lookup or readdirp) might not send an explicit
lookup on
    that object again (ex: NFS, samba, USS). If there is a replicate volume
    the replicas of the object are not in sync, then readdirp followed by fops
    lead data being served from the subvolume which is not in sync with latest
    data. And since lookup is needed to trigger self-heal on that object the
    consumers might keep getting wrong data until an explicit lookup is not

    Fuse handles this situation by sending an explicit lookup by itself (fuse
    xlator) on those inodes which are linked via readdirp, whenever a fop comes
    that inode.

    The same procedure is done in gfapi as well to address this situation.

    Thanks to shyam(srangana at redhat.com) for valuable inputs

    Change-Id: I64f0591495dddc1dea7f8dc319f2558a7e342871
    BUG: 1236009
    Signed-off-by: Raghavendra Bhat <raghavendra at redhat.com>
    Reviewed-on: http://review.gluster.org/11236
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>

Referenced Bugs:

[Bug 1236009] do an explicit lookup on the inodes linked in readdirp
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list