‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, November 15, 2018 5:57 AM, Ravishankar N <ravishan...@redhat.com> wrote:
> 1.Could you provide the getfattr output of the following 3 dirs from all > 3 nodes? > i)/data/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10 > ii)/data/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/dir11/ > iii)/data/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/dir11/oc_dir Sure, you will find below the getfattr output of all 3 directories from all 3 nodes. i)/data/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10 # NODE 1 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.myvol-pro-client-1=0x000000000000000000000000 trusted.gfid=0x7d7d2165f4804edf8c93de01c8768269 trusted.glusterfs.dht=0x000000010000000000000000ffffffff # NODE 2 trusted.gfid=0x7d7d2165f4804edf8c93de01c8768269 trusted.glusterfs.dht=0x000000010000000000000000ffffffff # NODE 3 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.myvol-pro-client-1=0x000000000000000000000000 trusted.gfid=0x7d7d2165f4804edf8c93de01c8768269 trusted.glusterfs.dht=0x000000010000000000000000ffffffff ii)/data/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/dir11/ # NODE 1 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.myvol-pro-client-1=0x000000000000000400000003 trusted.gfid=0x70c894ca422b4bceacf15cfb4669abbd trusted.glusterfs.dht=0x000000010000000000000000ffffffff # NODE 2 trusted.gfid=0x10ec1eb1c8544ff2a36c325681713093 trusted.glusterfs.dht=0x000000010000000000000000ffffffff # NODE 3 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.myvol-pro-client-1=0x000000000000000400000003 trusted.gfid=0x70c894ca422b4bceacf15cfb4669abbd trusted.glusterfs.dht=0x000000010000000000000000ffffffff iii)/data/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/dir11/oc_dir # NODE 1 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.myvol-pro-client-1=0x000000000000000300000003 trusted.gfid=0x25e2616b4fb64b2a89451afc956fff19 trusted.glusterfs.dht=0x000000010000000000000000ffffffff # NODE 2 trusted.gfid=0xd9ac192ce85e4402af105551f587ed9a trusted.glusterfs.dht=0x000000010000000000000000ffffffff # NODE 3 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.myvol-pro-client-1=0x000000000000000300000003 trusted.gfid=0x25e2616b4fb64b2a89451afc956fff19 trusted.glusterfs.dht=0x000000010000000000000000ffffffff > 2. Do you know the file (or directory) names corresponding to the other > 2 gfids in heal info output, i.e > gfid:aae4098a-1a71-4155-9cc9-e564b89957cf > gfid:3c92459b-8fa1-4669-9a3d-b38b8d41c360 > Please share the getfattr output of them as well. Unfortunately no. I tried the trick of mounting the volume with the mount option "aux-gfid-mount" in order to find the filename corresponding to the GFID and then using the following getfattr command: getfattr -n trusted.glusterfs.pathinfo -e text /mnt/g/.gfid/aae4098a-1a71-4155-9cc9-e564b89957cf this gave me the following output: trusted.glusterfs.pathinfo="(<DISTRIBUTE:myvol-pro-dht> (<REPLICATE:myvol-pro-replicate-0> <POSIX(/srv/glusterfs/myvol-pro/brick):node3:/srv/glusterfs/myvol-pro/brick/.glusterfs/aa/e4/aae4098a-1a71-4155-9cc9-e564b89957cf> <POSIX(/data/myvol-pro/brick):node1:/data/myvol-pro/brick/.glusterfs/aa/e4/aae4098a-1a71-4155-9cc9-e564b89957cf>))" then if I check the ".../brick/.glusterfs/aa/e4/aae4098a-1a71-4155-9cc9-e564b89957cf" on node 1 or node 3 it does not have any symlink to a file. Or am I looking at the wrong place maybe or there is another trick in order to find the GFID->filename? Regards, Mabi _______________________________________________ Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
