<div dir="ltr"><div><div>Each shard is also associated with a gfid.<br><br></div>So do you see the gfids of these 8 shards in the .glusterfs/indices/xattrop directory on any of the bricks?<br><br></div><div>-Krutika<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Apr 23, 2016 at 8:51 PM, Lindsay Mathieson <span dir="ltr"><<a href="mailto:lindsay.mathieson@gmail.com" target="_blank">lindsay.mathieson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 23/04/2016 11:14 PM, Krutika Dhananjay wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You'll see at least 2 paths listed for this inode number (because they're hardlinks of each other).<br>
One of them is the .glusterfs/... path which is internally maintained by gluster.<br>
<br>
The other path (or paths if the application itself created hard links to this file) is the one belonging to the main file that this shard belongs to.<br>
</blockquote>
<br>
<br></span>
Thanks Krutika, very useful.<br>
<br>
As part of testing today I stopped the volume and generated a md5sum for every shard on every brick. 20047 shards per brick, it took a while :)<br>
<br>
I then compared them and found there were 8 shards different and applying your algorithm found they were all from one file:<br>
<br>
/images/307/vm-307-disk-1.qcow2<br>
<br>
Is there anyway to launch a heal against just one file?<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Lindsay Mathieson<br>
<br>
</font></span></blockquote></div><br></div>