You will first need to restore connectivity between the gluster peers
for heal to work. So restart glusterd on all hosts as Strahil
mentioned, and check if "gluster peer status" returns the other nodes
as connected. If not, please check the glusterd log to see what's
causing the issue. Share the logs if we need to look at it, along with
the version info


On Sun, Mar 24, 2019 at 1:08 AM Strahil <[email protected]> wrote:
>
> Hi Andrea,
>
> The cluster volumes might have sharding enabled and thus files larger than 
> shard size can be recovered only  via cluster.
>
> You  can try to restart gluster on all nodes and force heal:
> 1. Kill gluster processes:
> systemctl stop glusterd
> /usr/share/glusterfs/scripts/stop-all-gluster-processes.sh
>
> 2. Start gluster:
> systemctl start glusterd
>
> 3. Force heal:
> for i in $(gluster volume list);  do gluster volume heal $i full  ; done
> sleep 300
> for i in $(gluster volume list);  do gluster volume heal $i info summary ; 
> done
>
> Best Regards,
> Strahil Nikolov
>
> On Mar 23, 2019 13:51, [email protected] wrote: > > During maintenance of 
> a machine the hosted engine crashed. > At that point there was no more chance 
> of managing anything. > > The VMs have paused, and were no longer manageable. 
> > I restarted the machine, but one point all the bricks were no longer 
> reachable. > > Now I am in a situation where the engine support is no longer 
> loaded. > > The gluster sees the peers connected and the services turned on 
> for the various bricks, but fails to heal the messages that I find for each 
> machine are the following > > # gluster volume heal engine info > Brick 
> 192.170.254.3:/bricks/engine/brick > > . > . > . > > Status: Connected Number 
> of entries: 190 > > Brick 192.170.254.4:/bricks/engine/brick > Status: Il 
> socket di destinazione non è connesso > Number of entries: - > > Brick 
> 192.170.254.6:/bricks/engine/brick > Status: Il socket di destinazione non è 
> connesso > Number of entries: - > > this for all the bricks (some have no 
> heal to do because the machines inside were turned off). > > In practice all 
> the bricks see only localhost as connected. > > How can I restore the 
> machines? > Is there a way to read data from the physical machine and export 
> it so that it can be reused? > Unfortunately we need to access that data. > > 
> Someone can help me. > > Thanks Andrea > 
> _______________________________________________ > Users mailing list -- 
> [email protected] > To unsubscribe send an email to [email protected] > 
> 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/[email protected]/message/EOIY7ZU4GOEMRUNY3CWF6R3JIQNPHLVA/
>  _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]/message/NMBDYBOY4TZB37I6O6VYBCVVGM5H3Y3F/
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/IUVVKMLEN5NLBCANUHA6QU5FVNXTHUJ6/

Reply via email to