Nux,
This can happen if there is a failure on both the files in write/truncate/ftruncate. I am wondering how the file went into such a state.
Could you throw some light as to what had happened?
Pranith.
----- Original Message -----
> From: "Nux!" <nux at li.nux.ro>
> To: "Pranith Kumar Karampuri" <pkarampu at redhat.com>
> Cc: "Gluster Users" <gluster-users at gluster.org>
> Sent: Monday, August 5, 2013 2:34:54 PM
> Subject: Re: No active sinks for performing self-heal on file
>
> On 05.08.2013 09:55, Pranith Kumar Karampuri wrote:
> > Is this the case in both the bricks of replicate? What is version of
> > glusterfs?
> >
> > Pranith.
>
> Yes, on both bricks it's the same:
>
> getfattr -d -m . -e hex
> /bricks/488_1152/.glusterfs/c5/25/c525c671-9855-4d3b-b1ab-dbc9fc7022cf
> getfattr: Removing leading '/' from absolute path names
> # file:
> bricks/488_1152/.glusterfs/c5/25/c525c671-9855-4d3b-b1ab-dbc9fc7022cf
> trusted.afr.488_1152-client-0=0x000000010000000000000000
> trusted.afr.488_1152-client-1=0x000000010000000000000000
> trusted.gfid=0xc525c67198554d3bb1abdbc9fc7022cf
> trusted.glusterfs.quota.2c056f93-fe6d-4927-8423-57d6ae80b9fb.contri=0x0000000000109000
>
> GlusterFS 3.4.0
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
