Most likely reason is that someone deleted these files manually from the brick directories. You must never access/modify the data from the brick directories directly, and all modifications must happen from a gluster client mount point. You may inspect the file contents to figure out if you still need those files. In the current position, those files can never be absorbed into the gluster volume.
Avati On Wed, Mar 12, 2014 at 3:48 AM, Chiku <[email protected]> wrote: > Hello, > > I have few question about folders .glusterfs/xx/xx/ > What I understand it's inside these folder there are files which are > hard-links to a regular files in the volume and the filename matches with > trusted.gfid of the regular file linked. > Do I miss anything else ? > > I have an replication volume with 3 nodes and right now the self-heal info > doesn't know. > with find . -path -type f -links -2, I find for : > node 1 : 0 > node 2 : 2 files > ./.glusterfs/b1/87/b187389f-0688-4828-b02a-e6f6e1daa4ea > ./.glusterfs/c0/06/c006fe90-43ce-43d1-a1ea-ae2db0f04637 > > -rw-r--r-- 1 1019 abc 206 Feb 17 02:50 ./.glusterfs/b1/87/b187389f- > 0688-4828-b02a-e6f6e1daa4ea > > node 3 : 644 files > > I check for node 2, these 2 gfid files don't match any trusted.gfid. > find . -noleaf -ignore_readdir_race -path ./.glusterfs -prune -o -type f > -print0 |xargs -0 getfattr -m . -n trusted.gfid -e hex |grep 'e6f6e1daa4ea' > On node 3, those gfid files don't match any trusted.gfid > > Can I remove those gfid files ? > That happended because someone removed the regular files without remonving > the gfid files ? > _______________________________________________ > Gluster-users mailing list > [email protected] > http://supercolony.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list [email protected] http://supercolony.gluster.org/mailman/listinfo/gluster-users
