Hi,
Can you restart the self-heal daemon by doing a `gluster volume start
bgl-vms-gfs force` and then launch the heal again? If you are seeing
different entries and counts each time you run heal info, there is
likely a network issue (disconnect) between the (gluster fuse?) mount
and the bricks of the volume leading to pending heals.
Also, there was a bug in arbiter volumes[1] that got fixed in glusterfs
3.12.15. It can cause VMs to pause when you reboot the arbiter node, so
it is recommended to upgrade to this gluster version.
HTH,
Ravi
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1637989
From: Dev Ops<sipandbite(a)hotmail.com>
Date: Mon, Nov 12, 2018 at 1:09 PM
Subject: [ovirt-users] Re: storage healing question
To:<users@ovirt.org>
Any help would be appreciated. I have since rebooted the 3rd gluster
node which is the arbiter. This doesn't seem to want to heal.
gluster volume heal bgl-vms-gfs info |grep Number
Number of entries: 68
Number of entries: 0
Number of entries: 68
_______________________________________________
Users mailing list --users(a)ovirt.org
To unsubscribe send an email tousers-leave(a)ovirt.org
Privacy
Statement:https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List
Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/XN...