[Gluster-users] trusted.ec.dirty attribute

Ashish Pandey aspandey at redhat.com
Fri Feb 9 03:35:24 UTC 2018

It is not at all good. 
It should be healed and dirty xattr should be set to all zero. 

Please provide all the xattrs of all the fragments of this file. 
Provide gluster v heal info 
Run gluster v heal <volname> and provide glustershd.logs 
Provide gluster v status <volame> 


----- Original Message -----

From: "Dmitri Chebotarov" <4dimach at gmail.com> 
To: "gluster-users" <Gluster-users at gluster.org> 
Sent: Friday, February 9, 2018 1:12:39 AM 
Subject: [Gluster-users] trusted.ec.dirty attribute 


I've got a problem on a EC volume where heal doesn't seem to work for just few files (heal info shows no progress for few days, Warning on the client mount) 

I ran 

getfattr -m . -d -e hex <brick>/<file> 

across all servers in the cluster and 'trusted.ec.dirty' attr is non-zero on all files which don't heal. 

Is it normal? Any way to correct it? 
It's my understanding it should be trusted.ec.dirty=0x00000000000000000000000000000000 for 'good' files. 

Out of 12 copies of the files, 11 have the same non-zero value (0x00000000001115920000000000000000), and 12th file has a different non-zero value. 

Thank you. 

Gluster-users mailing list 
Gluster-users at gluster.org 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180208/92395d57/attachment.html>

More information about the Gluster-users mailing list