2015-08-03 12:16 GMT+02:00 Mathieu Chateau <mathieu.chateau@xxxxxxx>: > You should start a heal > gluster volume xxx heal > or even a full one if not enough > gluster volume xxx heal full Thanks, I tried both but this not solved the problem: root@web1:~# ls -l /mnt/data/web/system/web/config.inc.php -rw-r--r-- 1 1010 1010 4041 Jul 31 17:42 /mnt/data/web/system/web/config.inc.php root@web2:~# ls -l /mnt/data/web/system/web/config.inc.php -rw-r--r-- 1 1010 1010 4041 Jul 24 09:20 /mnt/data/web/system/web/config.inc.php root@web3:~# ls -l /mnt/data/web/system/web/config.inc.php -rw-r--r-- 1 1010 1010 4041 Jul 24 09:20 /mnt/data/web/system/web/config.inc.php This is the heal info: root@web1:~# gluster volume heal data info Brick web1:/data/ <gfid:d5f6d18f-082f-40e9-bdd1-b7d7eee0ad6d> <gfid:376cc8a1-8592-4e3f-a47a-5d36fa62f6bc> Number of entries: 2 Brick web2:/data/ Number of entries: 0 Brick web3:/data/ Number of entries: 0 > I guess clients wrote some files while node was down or rebooting? I don't think this happened, because when I updated that file all nodes was running. _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
