<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body><div><div style="font-family: Calibri,sans-serif; font-size: 11pt;">The gluster.org debian wheezy repo installs 3.6.6 safely on px 3.4, I use it myself<br><br>Lindsay Mathieson </div></div><div dir="ltr"><hr><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">From: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;"><a href="mailto:udo.giacomozzi@indunet.it">Udo Giacomozzi</a></span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Sent: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;">15/10/2015 6:34 PM</span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">To: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;"><a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a></span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Subject: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;">[Gluster-users] Unnecessary healing in 3-node replication setup onreboot</span><br><br></div>Hello everybody,<br><br>I'm new to this list, apologies if I'm asking something stupid.. ;-)<br><br>I'm using GlusterFS on three nodes as the foundation for a 3-node <br>high-availability Proxmox cluster. GlusterFS is mostly used to store the <br>HDD images of a number of VMs and is accessed via NFS.<br><br>My problem is, that every time I reboot one of the nodes, Gluster starts <br>healing all of the files. Since they are quite big, it takes up to <br>~15-30 minutes to complete. It completes successfully, but I have to be <br>extremely careful not to migrate VMs around because that results in <br>corrupted files.<br><br>I've already posted this problem in #gluster IRC channel: <br>http://irclog.perlgeek.de/gluster/2015-10-01#i_11302365<br>and apparently it is a bug that *could* have been resolved in more <br>recent releases of Gluster.<br><br>I'm currently running the most recent version of the Proxmox 3.4 <br>repository (Gluster 3.5.2; based on Debian Wheezy) . Upgrading Gluster <br>means some work (build from source, probably) and potetial risk, so I'd <br>like to be sure that using Gluster 3.7 will solve this problem and not <br>cause any other problems.<br><br>Somebody has more detailed information about this bug? Perhaps is there <br>any way to work around it?<br><br>Thank you very much,<br>Udo<br><br><br>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>http://www.gluster.org/mailman/listinfo/gluster-users<br></body></html>