This is regarding glusterfs(3.7.6) issue we are facing at our end. We have a logging file which saves logs of the events for two node and this file are in sync using replica volume. When we restart the nodes , we see that log file of one board is not in the sync . How to reproduce: 1.Create a volume consisting of two bricks as replica type. 2.There is a mount point to the volume in each brick. 3.The two brick write the same logging file by the mount point of their own. 4.Reboot two nodes one by one. May be reboot A node firstly and B node continued to write the logging file through their mount point. 5.After two node startup, the logging file is quite different looked by the mount point of their own.?Does its format corrupted means different that is not in the sync?? 6.heal is not work in this case. I have checked the outputs of some gluster commands to see if the split brain entries are present , but I don't see any significant outcome from that. ============================================================================================= $ lhsh 000300 /usr/sbin/gluster volume heal c_glusterfs info split-brain 0003: Brick 192.32.0.48:/opt/lvmdir/c2/brick 0003: Number of entries in split-brain: 0 0003: Brick 192.32.1.144:/opt/lvmdir/c2/brick 0003: Number of entries in split-brain: 0 ============================================================================================= $ lhsh 002500 /usr/sbin/gluster volume heal c_glusterfs info split-brain 0025: Brick 192.32.0.48:/opt/lvmdir/c2/brick 0025: Number of entries in split-brain: 0 0025: Brick 192.32.1.144:/opt/lvmdir/c2/brick 0025: Number of entries in split-brain: 0 $ Thanks, Xin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160205/2d644622/attachment.html>