The problem here is that the accounting xattr in the backend becomes FFFFF...
This happens likely due to an underflow (value goes below 0) on some operation like rm/unlink/truncate/mv. We would be adding defensive checks to prevent this, but that will not solve the accounting issue.This is a race and we do not have a consistent reproducer for it yet. Could you describe the operations that were being done on the volume when u ran into this?
Due to the way quota works, if xattr of any directory goes wrong they get bubbled up to all its ancestors. So, it would also help if we can identify the lowest directory in the tree where the xattr has gone wrong and then try to find the operations on that particular directory.
Could you also share the xattr values on all bricks: find . | xargs getfattr -d -m. -e hex
To recover from this you could do a quota disable and enable.
Thanks and Regards,
Sanoj
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
