So even killall situation eventually kills VM (I/O errors). Gandalf, isn't possible server hard-crash too much? I mean if reboot reliably kills the VM, there is no doubt network crash or poweroff will as well. I am tempted to test this setup on DigitalOcean to eliminate possibility of my hardware/network. But if Diego is able to reproduce the "reboot crash", my doubts of hardware/network problems are close to none. -ps On Fri, Sep 8, 2017 at 1:11 PM, Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx> wrote: > 2017-09-08 13:07 GMT+02:00 Pavel Szalbot <pavel.szalbot@xxxxxxxxx>: >> >> OK, so killall seems to be ok after several attempts i.e. iops do not stop >> on VM. Reboot caused I/O errors after maybe 20 seconds since issuing the >> command. I will check the servers console during reboot to see if the VM >> errors appear just after the power cycle and will try to crash the VM after >> killall again... >> > > Also try to kill the Gluster VM without killing glusterfsd, simulating a > server hard-crash . Or try to remove the network interface. > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
