Bug 1138922

REVIEW: http://review.gluster.org/8712 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#2) for review on release-3.5 by Niels de Vos (ndevos)

COMMIT: http://review.gluster.org/8712 committed in release-3.5 by Niels de Vos (ndevos) 
------
commit b459b74b7191783a1392070bc3cd02ffad154868
Author: Venkatesh Somyajulu <vsomyaju>
Date:   Wed Sep 10 20:57:08 2014 +0530

    dht/rebalance: Do not allow rebalance when gfid mismatch found
    
    Due to race condition, it may so happen that, gfid obtained
    in readdirp and gfid found by lookup are different for a given
    name. in that case do no allow the rebalance.
    
    Readdirp of an entry will bring the gfid, which will be stored
    in the inode through inode_link, and when lookup is done and
    gfid brought by lookup is different from the one stored in the
    inode, client3_3_lookup_cbk will return ESATLE and error will be
    captured by rebalance process.
    
    Cherry picked from commit 72c7afcd:
    > Change-Id: Iad839177ef9b80c1dd0e87f3406bcf4cb018e6fa
    > BUG: 1104653
    > Signed-off-by: Venkatesh Somyajulu <vsomyaju>
    > Reviewed-on: http://review.gluster.org/7973
    > Reviewed-by: Shyamsundar Ranganathan <srangana>
    > Tested-by: Gluster Build System <jenkins.com>
    > Reviewed-by: Krutika Dhananjay <kdhananj>
    > Reviewed-by: Vijay Bellur <vbellur>
    
    Also merged the oneline change from commit de22a20a:
    > Change-Id: I979b7333efa93b1e8f4c73ccf048d48e308f9289
    > BUG: 1104653
    > Signed-off-by: Venkatesh Somyajulu <vsomyaju>
    > Reviewed-on: http://review.gluster.org/8073
    > Reviewed-by: Krutika Dhananjay <kdhananj>
    > Tested-by: Gluster Build System <jenkins.com>
    > Reviewed-by: Raghavendra G <rgowdapp>
    > Reviewed-by: Vijay Bellur <vbellur>
    
    Change-Id: Iad839177ef9b80c1dd0e87f3406bcf4cb018e6fa
    BUG: 1138922
    Signed-off-by: Nithya Balachandran <nbalacha>
    Reviewed-on: http://review.gluster.org/8712
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Niels de Vos <ndevos>

The first (and last?) Beta for GlusterFS 3.5.3 has been released [1]. Please verify if the release solves this bug report for you. In case the glusterfs-3.5.3beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-October/018990.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

The second Beta for GlusterFS 3.5.3 has been released [1]. Please verify if the release solves this bug report for you. In case the glusterfs-3.5.3beta2 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions have been made available on [2] to make testing easier.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019359.html
[2] http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.5.3beta2/

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.3, please reopen this bug report.

glusterfs-3.5.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/announce/2014-November/000042.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/