Bug 1139103

REVIEW: http://review.gluster.org/8713 (DHT/readdirp: Directory not shown/healed on mount point if exists               on single brick(non first up subvolume).) posted (#1) for review on release-3.5 by N Balachandran (nbalacha)

COMMIT: http://review.gluster.org/8713 committed in release-3.5 by Niels de Vos (ndevos) 
------
commit c53aab61b8ff5957a306f499565be0ab3ff0fb78
Author: Susant Palai <spalai>
Date:   Wed Sep 10 21:24:41 2014 +0530

    DHT/readdirp: Directory not shown/healed on mount point if exists
                  on single brick(non first up subvolume).
    
    Problem: If snapshot is taken, when mkdir has succeeded only on
    hashed_subvolume, then after restoring snapshot the directory
    is not shown on mount point.
    
    Why:    dht_readdirp takes only those directory entries in to
    account, which are present on first_up_subvolume. Hence, if the
    "hashed subvolume" is not same as first_up_subvolume, it wont be listed
    on mount point and also not healed.
    
    Solution:
    Case 1: (Rebalance not running)If hashed subvolume is NULL or down then
    filter in first_up_subvolume. Other wise the corresponding hashed subvolume
    will take care of the directory entry.
    
    Case 2: If readdirp_optimize option is turned on then read from first_up_subvol
    
    Change-Id: Idaad28f1c9f688dbfb1a8a3ab8b244510c02365e
    BUG: 1139103
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/7599
    Reviewed-by: Raghavendra G <rgowdapp>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>
    (cherry picked from commit b8f3aab95f01ac7d590a5ba490e890d9cf8c2e50)
    Signed-off-by: Nithya Balachandran <nbalacha>
    Reviewed-on: http://review.gluster.org/8713
    Reviewed-by: Jeff Darcy <jdarcy>
    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/