REVIEW: http://review.gluster.org/10877 (glusterd: do not show pid of brick in volume status if brick is down.) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10877 (glusterd: do not show pid of brick in volume status if brick is down.) posted (#3) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10877 (glusterd: do not show pid of brick in volume status if brick is down.) posted (#4) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/10877 (glusterd: do not show pid of brick in volume status if brick is down.) posted (#5) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/10877 (glusterd: do not show pid of brick in volume status if brick is down.) posted (#6) for review on master by Gaurav Kumar Garg (ggarg)
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user