Hi,
thanks.. this is very useful…..
Met vriendelijke groet / kind regards,
Sander Zijlstra
| Linux Engineer | SURFsara | Science Park 140 | 1098XG Amsterdam | T +31 (0)6
43 99 12 47 | sander.zijls...@surfsara.nl mailto:sander.zijls...@surfsara.nl
| www.surfsara.nl http://www.surfsara.nl/ |
On 04/13/2015 07:20 PM, Sander Zijlstra wrote:
Hi,
thanks, I missed that one….
Does this mean that I can rely on looking at “volume heal info” output
to notice issues?
I regularly see those numbers return “0” so I can rely on that meaning
that no files failed healing?
That is
LS,
I recently upgraded to 3.6.2 and I noticed that the info command for
heal-failed is not working:
# gluster volume heal gv0 info failed
Usage: volume heal VOLNAME [{full | statistics {heal-count {replica
hostname:brickname}} |info {healed | heal-failed | split-brain}}]
[root@v39-app-01 ~]#
On 04/13/2015 06:23 PM, Sander Zijlstra wrote:
LS,
I recently upgraded to 3.6.2 and I noticed that the info command for
heal-failed is not working:
# gluster volume heal gv0 info failed
Usage: volume heal VOLNAME [{full | statistics {heal-count {replica
hostname:brickname}} |info {healed
Hi,
thanks, I missed that one….
Does this mean that I can rely on looking at “volume heal info” output to
notice issues?
I regularly see those numbers return “0” so I can rely on that meaning that no
files failed healing?
Off course as per the bug report I still need to check the
