Running a two node replicated volume with GlusterFS 3.5.3, I've noticed that one node couldn't reach its time server, and is now about 80 sec behind the other node. I'm a bit afraid of running a ntpdate to force the clock back on sync, could such a big jump forward cause gluster to think the files are out dated and start a heal ? Only meta-data heal maybe ? This cluster is hosting critical data, and I don't want to take a risk. What could happen if I just leave it as is, with a big time offset between the two nodes ? Could this explain why I see continuous healed file (see my previous thread "info healed show files being healed all the time") ? Thanks for your advice. Cheers Daniel -- Logo FWS *Daniel Berteaud* FIREWALL-SERVICES SAS. Soci?t? de Services en Logiciels Libres Tel : 05 56 64 15 32 Visio : http://vroom.im/dani /www.firewall-services.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160419/928209ca/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature_mail_fws.png Type: image/png Size: 14520 bytes Desc: not available URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160419/928209ca/attachment.png>