Re: How to resolve gfid (and .glusterfs symlink) for a deleted file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 21 Nov 2014 11:20:19 -0500 (EST)
Ben England <bengland@xxxxxxxxxx> wrote:
> Nux,
> 
> Those thousands of entries all would match "-links 2" but not "-links
> 1"  The only entry in .glusterfs that would match is the entry where
> you deleted the file from the brick.  That's how hardlinks work -
> when you create a regular file, the link count is increased to 1
> (since the directory entry now references the inode), and when you
> create an additional hard link to the same file, the link count is
> increased to 2.   Try this with the "stat your-file" command and look
> at the link count, watch how it changes.  The "find" command that I
> gave you just tracks down the one hardlink that you want and nothing
> else.

We really need a "Tips and Tricks when working with GlusterFS" area on
the wiki.  This is exactly the right kind of info for that. :D

+ Justin

-- 
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux