Description of problem: gstatus -b does not provide any information on self-heal For example: [root@mater gstatus]# gstatus -b Product: RHSS v2.1 u5 Capacity: 293.00 GiB(raw bricks) Status: HEALTHY 15.00 GiB(raw used) Glusterfs: 3.4.0.70rhs 146.00 GiB(usable from volumes) OverCommit: No [root@mater gstatus]# gstatus Product: RHSS v2.1 u5 Capacity: 293.00 GiB(raw bricks) Status: HEALTHY 15.00 GiB(raw used) Glusterfs: 3.4.0.70rhs 146.00 GiB(usable from volumes) OverCommit: No [root@mater gstatus]# In the above output gstatus and gstatus -b are much the same. If I use -b with -v I see information on self-heal. [root@mater gstatus]# gstatus -bv Product: RHSS v2.1 u5 Capacity: 293.00 GiB(raw bricks) Status: HEALTHY 15.00 GiB(raw used) Glusterfs: 3.4.0.70rhs 146.00 GiB(usable from volumes) OverCommit: No Volume Information upgrade UP - 4/4 bricks up - Distributed-Replicate Capacity: (4% used) 7.00 GiB/146.00 GiB (used/total) Self Heal: 4/ 4 Heal backlog of 8866 files Tasks Active: None Protocols: glusterfs:on NFS:on SMB:on Gluster Clients : 1
So is the request that -b is only allowed on conjunction with -a or -v? You're right - only when you look at the volume level, does -b become relevant. Cheers, PC
Paul, yes. Thanks.
Lot of time since no activity on this bug. We have either fixed it already or it is mostly not critical anymore! Please re-open the bug if the issue is burning for you, or you want to take the bug to closure with fixes.