> > Great, that worked. ie gluster volume set VOL > cluster.server-quorum-type none > > Although I did get an error of "Volume set: failed: Commit failed on > localhost, please check the log files for more details" > > but then I noticed that volume immediately came back up and I was able > to mount the single remaining node and access those files. > > So you need to do both settings in my scenario. > Thanks for testing that, it's good to know that the solution actually works ! We don't use arbiters so I guess we're okay on that side though, but if it ever explodes again I'm glad to know there is a way to quickly get back some service, even if that means re-creating a new volume later on.
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
