REVIEW: http://review.gluster.org/10482 (glusterd: volume info should not show "feature.scrub: resume" if scrub resumed) posted (#2) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

COMMIT: http://review.gluster.org/10482 committed in release-3.7 by Kaushal M (kaushal) 
------
commit f972f21fa810f4c14701a14b8a1cd1f3db92f313
Author: Gaurav Kumar Garg <ggarg>
Date:   Sat Apr 11 17:05:45 2015 +0530

    glusterd: volume info should not show "feature.scrub: resume" if scrub resumed
    
    If bitrot is enable on the volume and if user paused the scrub process and then
    resume the scrub process then command #gluster volume info <VOLNAME> should show
    status of option features.scrub: Active.
    
    If bitrot is enable on the volume and user disable the bitrot on the volume then
    command #gluster volume info <VOLNAME> should show status of option
    features.scrub: Inactive.
    
    If bitrot is enable on the volume and user paused the scrub porcess then command
    gluster volume info <VOLNAME> should show the status of option
    features.scrub: pause.
    
    Change-Id: I55972eef3b8570b7cb05dc28700d4e28dc45a86a
    BUG: 1218036
    Signed-off-by: Gaurav Kumar Garg <ggarg>
    Reviewed-on: http://review.gluster.org/10207
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Venky Shankar <vshankar>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    (cherry picked from commit 6faf89f4179c452be20f02966b9722641938599d)
    Reviewed-on: http://review.gluster.org/10482
    Tested-by: NetBSD Build System
    Reviewed-by: Kaushal M <kaushal>

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.7.0, please open a new bug report.

glusterfs-3.7.0 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

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.7.0, please open a new bug report.

glusterfs-3.7.0 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

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.7.0, please open a new bug report.

glusterfs-3.7.0 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

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.7.0, please open a new bug report.

glusterfs-3.7.0 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user