On Thu, Sep 22, 2016 at 8:33 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Thu, Sep 22, 2016 at 07:20:26PM +0530, Pranith Kumar Karampuri wrote:
> On Thu, Sep 22, 2016 at 12:51 PM, Ravishankar N
> <[1]ravishankar@xxxxxxxxxx> wrote:
>
> On 09/22/2016 12:38 PM, Pasi KÀrkkÀinen wrote:
>
> 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=0x756e636f6e66696e65645f753a6f Sure. Should I file the bug on redhat bugzilla?626a6563745f723a756e6c6162656c 65645f743a733000
>
> 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 ?
>
> Do you want to raise a bug for this? We would love to if you don't have
> the time to make sure we address this.
>
-- Pasi
--
Pranith
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users