REVIEW: https://review.gluster.org/17492 (glusterfsd: Deletion of brick dir throw emerg msgs after stop volume) posted (#1) for review on master by MOHIT AGRAWAL (moagrawa)

COMMIT: https://review.gluster.org/17492 committed in master by Jeff Darcy (jeff.us) 
------
commit 5b82f173ba337b2fe06846c2a0e5f35d1ff53357
Author: Mohit Agrawal <moagrawa>
Date:   Thu Jun 8 13:04:42 2017 +0530

    glusterfsd: Deletion of brick dir throw emerg msgs after stop volume
    
    Problem: Deletion of brick directories throw emerg messages after stop
             volume while brick mux is enabled.
    
    Solution: Modify the posix health check monitor thread code to
              handled correctly.
    
    BUG: 1459781
    Signed-off-by: Mohit Agrawal <moagrawa>
    
    Change-Id: I2d22a84f9a98b0da261e5fb7850ba1368f3601d7
    Reviewed-on: https://review.gluster.org/17492
    Tested-by: MOHIT AGRAWAL <moagrawa>
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Raghavendra Talur <rtalur>
    Reviewed-by: Jeff Darcy <jeff.us>

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

glusterfs-3.12.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://lists.gluster.org/pipermail/announce/2017-September/000082.html
[2] https://www.gluster.org/pipermail/gluster-users/