first of all, links in .glusterfs are HARD links not symlinks. So the file is not actually deleted, since the local filesystem keeps a count of references to the inode and won't release the inode until the ref count reaches zero. I tried this, it turns out you can find it with # find /your/brick/directory/.glusterfs -links 1 -type f You use "type f" because it's a hard link to a file, and you don't want to look at directories or "." or ".." . Once you find the link, you can copy the file off somewhere, and then delete the link. At that point, regular self-heal could repair it (i.e. just do "ls" on the file from a Gluster mountpoint). ----- Original Message ----- > From: "Nux!" <nux@xxxxxxxxx> > To: "Gluster Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Friday, November 21, 2014 10:34:09 AM > Subject: How to resolve gfid (and .glusterfs symlink) for a deleted file > > Hi, > > I deleted a file by mistake in a brick. I never managed to find out its gfid > so now I have a rogue symlink in .glusterfs pointing to it (if I got how it > works). > Any way I can discover which is this file and get rid of it? > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
