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>
---
Ashish
From: "Dmitri Chebotarov" <4dimach@xxxxxxxxx>
To: "gluster-users" <Gluster-users@xxxxxxxxxxx>
Sent: Friday, February 9, 2018 1:12:39 AM
Subject: trusted.ec.dirty attribute
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
To: "gluster-users" <Gluster-users@xxxxxxxxxxx>
Sent: Friday, February 9, 2018 1:12:39 AM
Subject: trusted.ec.dirty attribute
Hi
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@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
