Ok so I ran and rsync from host2 over to host3 for the .meta files only and that seems to have worked: 98d64fb4-df01-4981-9e5e-62be6ca7e07c.meta ed569aed-005e-40fd-9297-dd54a1e4946c.meta [root@host1 ~]# gluster vol heal engine info Brick host1.grupolucerna.local:/gluster_bricks/engine/engine Status: Connected Number of entries: 0 Brick host3:/gluster_bricks/engine/engine Status: Connected Number of entries: 0 Brick host3:/gluster_bricks/engine/engine Status: Connected Number of entries: 0 In this case I did not have to stop/start the ovirt-ha-broker and ovirt-ha-agent I still see the issue of the OVF, wondering if I should just rsync the whole /gluster_bricks/engine/engine directory from host3 over to host1 and 2 because of the following 1969 timestamps: I 1969 as the timestamps on some directories in host1: /gluster_bricks/engine/engine/7a68956e-3736-46d1-8932-8576f8ee8882/images: drwxr-xr-x. 2 vdsm kvm 8.0K Dec 31 1969 b8ce22c5-8cbd-4d7f-b544-9ce930e04dcd drwxr-xr-x. 2 vdsm kvm 8.0K Dec 31 1969 86196e10-8103-4b00-bd3e-0f577a8bb5b2 on host2 I see the same: drwxr-xr-x. 2 vdsm kvm 8.0K Dec 31 1969 b8ce22c5-8cbd-4d7f-b544-9ce930e04dcd drwxr-xr-x. 2 vdsm kvm 8.0K Dec 31 1969 86196e10-8103-4b00-bd3e-0f577a8bb5b2 but for host3: I see a valid timestamp drwxr-xr-x. 2 vdsm kvm 149 Feb 16 09:43 86196e10-8103-4b00-bd3e-0f577a8bb5b2 drwxr-xr-x. 2 vdsm kvm 149 Feb 16 09:45 b8ce22c5-8cbd-4d7f-b544-9ce930e04dcd If we take a close look it seems that host3 has a valid timestamp but host1 and host2 have a 1969 date. Thoughts? thanks, Adrian