<html><body><div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000"><div>Could you share the output of 'gluster volume info', and also information as to which node went down on reboot?<br></div><div><br></div><div>-Krutika<br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"André Bauer" <abauer@magix.net><br><b>To: </b>"gluster-users" <gluster-users@gluster.org><br><b>Cc: </b>gluster-devel@gluster.org<br><b>Sent: </b>Friday, October 23, 2015 12:15:04 AM<br><b>Subject: </b>[Gluster-users] VM fs becomes read only when one gluster node goes down<br><div><br></div>Hi,<br><div><br></div>i have a 4 node Glusterfs 3.5.6 Cluster.<br><div><br></div>My VM images are in an replicated distributed volume which is accessed<br>from kvm/qemu via libgfapi.<br><div><br></div>Mount is against storage.domain.local which has IPs for all 4 Gluster<br>nodes set in DNS.<br><div><br></div>When one of the Gluster nodes goes down (accidently reboot) a lot of the<br>vms getting read only filesystem. Even when the node comes back up.<br><div><br></div>How can i prevent this?<br>I expect that the vm just uses the replicated file on the other node,<br>without getting ro fs.<br><div><br></div>Any hints?<br><div><br></div>Thanks in advance.<br><div><br></div>-- <br>Regards<br>André Bauer<br><div><br></div>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>http://www.gluster.org/mailman/listinfo/gluster-users</blockquote><div><br></div></div></body></html>