[ovirt-users] Re: OVirt Gluster Fail

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 <gfid:cf9eac3a-b532-4557-8d81-2fca07a0d3f5> . . . <gfid:cf5eaf66-b532-5444-8d81-2fca07a0d3f5> 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