Each shard is also associated with a gfid. So do you see the gfids of these 8 shards in the .glusterfs/indices/xattrop directory on any of the bricks? -Krutika On Sat, Apr 23, 2016 at 8:51 PM, Lindsay Mathieson < lindsay.mathieson at gmail.com> wrote:> On 23/04/2016 11:14 PM, Krutika Dhananjay wrote: > >> You'll see at least 2 paths listed for this inode number (because they're >> hardlinks of each other). >> One of them is the .glusterfs/... path which is internally maintained by >> gluster. >> >> 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. >> > > > Thanks Krutika, very useful. > > 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 :) > > I then compared them and found there were 8 shards different and applying > your algorithm found they were all from one file: > > /images/307/vm-307-disk-1.qcow2 > > Is there anyway to launch a heal against just one file? > > -- > Lindsay Mathieson > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160423/23953b9a/attachment.html>
On 24/04/2016 1:24 AM, Krutika Dhananjay wrote:> Each shard is also associated with a gfid. > > So do you see the gfids of these 8 shards in the > .glusterfs/indices/xattrop directory on any of the bricks?The .glusterfs/indices/xattrop directory is empty on all three bricks - you mean a file listing? -- Lindsay Mathieson
On 24/04/2016 1:24 AM, Krutika Dhananjay wrote:> Each shard is also associated with a gfid. > > So do you see the gfids of these 8 shards in the > .glusterfs/indices/xattrop directory on any of the bricks?There were no files at all in the xattrop dir. Also I did a spot check of the extended attr of the shards in question and they did not look right (as I understand them). Shouldn't trusted.afr.datastore4-client-0/1/2 be set for all shards (excluding their brick index) ssh root at vng getfattr -d -m . -e hex /tank/vmdata/datastore4/.shard/744c5059-303d-4e82-b5be-0a5f53b1aeff.1172 # file: tank/vmdata/datastore4/.shard/744c5059-303d-4e82-b5be-0a5f53b1aeff.1172 trusted.afr.datastore4-client-2=0x000000000000000000000000 trusted.afr.dirty=0x000000000000000000000000 trusted.bit-rot.version=0x0400000000000000571632100008cfbf trusted.gfid=0xac4dc6375d6a4b0c90763ffb5314a5a3 getfattr: Removing leading '/' from absolute path names root at vna:~# ssh root at vna getfattr -d -m . -e hex /tank/vmdata/datastore4/.shard/744c5059-303d-4e82-b5be-0a5f53b1aeff.1172 # file: tank/vmdata/datastore4/.shard/744c5059-303d-4e82-b5be-0a5f53b1aeff.1172 trusted.afr.dirty=0x000000000000000000000000 trusted.bit-rot.version=0x0500000000000000571626b8000316f0 trusted.gfid=0xac4dc6375d6a4b0c90763ffb5314a5a3 getfattr: Removing leading '/' from absolute path names root at vna:~# ssh root at vnb getfattr -d -m . -e hex /tank/vmdata/datastore4/.shard/744c5059-303d-4e82-b5be-0a5f53b1aeff.1172 # file: tank/vmdata/datastore4/.shard/744c5059-303d-4e82-b5be-0a5f53b1aeff.1172 trusted.afr.datastore4-client-2=0x000000000000000000000000 trusted.afr.dirty=0x000000000000000000000000 trusted.bit-rot.version=0x040000000000000057160faa000e0632 trusted.gfid=0xac4dc6375d6a4b0c90763ffb5314a5a3 -- Lindsay Mathieson