Bug 1047331

REVIEW: http://review.gluster.org/6618 (dht: Ignore directory with missing xattrs, which have err == 0, and start == stop) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)

In Anshi release, xattrs was written with 0-0% hash range when there is no layout for the directory.

Current behavior is, we ignore the directories when the layout is absent and do not write xattrs. 
This change is introduced by the patch: http://review.gluster.org/4668/

Logging for missed layout need to be fixed when err == 0, and start == stop.

COMMIT: http://review.gluster.org/6618 committed in master by Anand Avati (avati) 
------
commit dd1f4a480511c4785d004c06dd9c41ba54f05143
Author: Vijaykumar M <vmallika>
Date:   Mon Dec 30 18:06:56 2013 +0530

    dht: Ignore directory with missing xattrs, which have err == 0, and start == stop
    
    From the history (Patch: http://review.gluster.org/4668/)
    
    When subvols-per-directory is < available subvols, then there are layouts
    which are not populated. This leads to incorrect identification of holes or
    overlaps. We need to ignore layouts, which have err == 0, and start == stop.
    In the current scenario (start == stop == 0).
    
    Additionally, in layout-merge, treat missing xattrs as err = 0. In case of
    missing layouts, anomalies will reset them.
    
    For any other valid subvoles, err != 0 in case of layouts being zeroed out.
    Also reverted back dht_selfheal_dir_xattr, which does layout calculation only
    on subvols which have errors.
    
    Change-Id: Idb72a869f1a6f103046bb7e6fe0019f6ac853fd4
    BUG: 1047331
    Signed-off-by: Vijaykumar M <vmallika>
    Reviewed-on: http://review.gluster.org/6618
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana>
    Reviewed-by: Anand Avati <avati>

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 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-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users