Gluster users - Sep 2016 - gluster 3.7 healing errors (no data available, buf->ia_gfid is null)

On 09/21/2016 10:54 PM, Pasi K?rkk?inen wrote:
> Let's see.
>
> # getfattr -m . -d -e hex /bricks/vol1/brick1/foo
> getfattr: Removing leading '/' from absolute path names
> # file: bricks/vol1/brick1/foo
>
security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a756e6c6162656c65645f743a733000
>
> So hmm.. no trusted.gfid it seems.. is that perhaps because this node was
down when the file was created?
No, even if that were the case, the gfid should have been set while 
healing the file to this node.
Can you try doing a setfattr -n trusted.gfid -v 
0xc1ca778ed2af4828b981171c0c5bd45e on the file. and launch heal again?
What about the .glusterfs hardlink- does that exist?

-Ravi
>
>
> On another node:
>
> # getfattr -m . -d -e hex /bricks/vol1/brick1/foo
> getfattr: Removing leading '/' from absolute path names
> # file: bricks/vol1/brick1/foo
>
security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000
> trusted.afr.dirty=0x000000000000000000000000
> trusted.afr.gvol1-client-1=0x000016620000000100000000
> trusted.bit-rot.version=0x020000000000000057e00db5000624ed
> trusted.gfid=0xc1ca778ed2af4828b981171c0c5bd45e
>
> So there we have the gfid..
>
> How do I fix this and allow healing process to continue/finish..  ?
>
>
> Thanks,
>
> -- Pasi

On Thu, Sep 22, 2016 at 09:58:25AM +0530, Ravishankar N
wrote:
> On 09/21/2016 10:54 PM, Pasi K?rkk?inen wrote:
> >Let's see.
> >
> ># getfattr -m . -d -e hex /bricks/vol1/brick1/foo
> >getfattr: Removing leading '/' from absolute path names
> ># file: bricks/vol1/brick1/foo
>
>security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a756e6c6162656c65645f743a733000
> >
> >So hmm.. no trusted.gfid it seems.. is that perhaps because this node
was down when the file was created?
>
> No, even if that were the case, the gfid should have been set while
> healing the file to this node.
> Can you try doing a setfattr -n trusted.gfid -v
> 0xc1ca778ed2af4828b981171c0c5bd45e on the file. and launch heal
> again?
> What about the .glusterfs hardlink- does that exist?
> 
It seems there's no hardlink.. nothing in
/bricks/vol1/brick1/.glusterfs/c1/ca/ directory.

Now I manually set the trusted.gfid value on the file, and launched heal again,
and now gluster was able to heal it OK! Healing is now fully complete, and no
out-of-sync files anymore.

Any idea what caused the missing trusted.gfid ? 



Thanks a lot!

-- Pasi