search for: stomith

...lf. Pavel alluded to something like that when describing his problem. That is where replica 3 helps. In theory, with replica 3, you could lose 2 nodes and still have a reasonable copy of your VM, though you've lost quorum and are still down. At that point, *I* would kill the two bad nodes (STOMITH) to prevent them from coming back AND turn off quorum. You could then run on the single node until you can save/copy those VM images, preferably by migrating off that volume completely. Create a remote pool using SSHFS if you have nothing else available. THEN I would go back and fix the gluster...

...hing like that when describing his > problem. > > That is where replica 3 helps. In theory, with replica 3, you could > lose 2 nodes and still have a reasonable copy of your VM, though > you've lost quorum and are still down. At that point, *I* would kill > the two bad nodes (STOMITH) to prevent them from coming back AND turn > off quorum. You could then run on the single node until you can > save/copy those VM images, preferably by migrating off that volume > completely. Create a remote pool using SSHFS if you have nothing else > available. THEN I would go back and...

Il 25-08-2017 08:32 Gionatan Danti ha scritto: > Hi all, > any other advice from who use (or do not use) Gluster as a replicated > VM backend? > > Thanks. Sorry, I was not seeing messages because I was not subscribed on the list; I read it from the web. So it seems that Pavel and WK have vastly different experience with Gluster. Any plausible cause for that difference? > WK

Il 23-08-2017 18:51 Gionatan Danti ha scritto: > Il 23-08-2017 18:14 Pavel Szalbot ha scritto: >> Hi, after many VM crashes during upgrades of Gluster, losing network >> connectivity on one node etc. I would advise running replica 2 with >> arbiter. > > Hi Pavel, this is bad news :( > So, in your case at least, Gluster was not stable? Something as simple > as an