----- Original Message ----- > From: "mabi" <mabi@xxxxxxxxxxxxx> > To: "Gluster Users" <gluster-users@xxxxxxxxxxx> > Sent: Monday, August 21, 2017 9:28:24 AM > Subject: self-heal not working > > Hi, > > I have a replicat 2 with arbiter GlusterFS 3.8.11 cluster and there is > currently one file listed to be healed as you can see below but never gets > healed by the self-heal daemon: > > Brick node1.domain.tld:/data/myvolume/brick > /data/appdata_ocpom4nckwru/preview/1344699/64-64-crop.png > Status: Connected > Number of entries: 1 > > Brick node2.domain.tld:/data/myvolume/brick > /data/appdata_ocpom4nckwru/preview/1344699/64-64-crop.png > Status: Connected > Number of entries: 1 > > Brick node3.domain.tld:/srv/glusterfs/myvolume/brick > /data/appdata_ocpom4nckwru/preview/1344699/64-64-crop.png > Status: Connected > Number of entries: 1 > > As once recommended on this mailing list I have mounted that glusterfs volume > temporarily through fuse/glusterfs and ran a "stat" on that file which is > listed above but nothing happened. > > The file itself is available on all 3 nodes/bricks but on the last node it > has a different date. By the way this file is 0 kBytes big. Is that maybe > the reason why the self-heal does not work? Is the file actually 0 bytes or is it just 0 bytes on the arbiter(0 bytes are expected on the arbiter, it just stores metadata)? Can you send us the output from stat on all 3 nodes: $ stat <file on back end brick> $ getfattr -d -m - <file on back end brick> $ stat <file from gluster mount> Lets see what things look like on the back end, it should tell us why healing is failing. -b > > And how can I now make this file to heal? > > Thanks, > Mabi > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://lists.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
