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

bugzilla at redhat.com bugzilla at redhat.com
Mon Jul 6 15:14:08 UTC 2015


--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11545 committed in release-3.7 by Niels de
Vos (ndevos at redhat.com) 
commit 69c434432853e2ba1ee53296f05c6a54ab300d02
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

              Backport of http://review.gluster.org/11236

    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: I4230fae8e0b01a95c056282b08ed30832d4804a7
    BUG: 1240190
    Signed-off-by: Raghavendra Bhat <raghavendra at redhat.com>
    Reviewed-on: http://review.gluster.org/11545
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>

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