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

Ravishankar N ravishankar at redhat.com
Thu Sep 22 04:28:25 UTC 2016


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




More information about the Gluster-users mailing list