On 10/28/2014 02:05 PM, Xavier Hernandez wrote:
On 10/28/2014 04:30 AM, Raghavendra Gowdappa wrote:
We use extended attribute with key "trusted.glusterfs.quota.size" to
get the size of a directory/file. The value for this key is probed in
lookup and getxattr calls. You can implement logic to handle this key
appropriately in disperse xlator to give a proper size to higher
layers. In your existing implementation you might have been probably
passing xattrs from one of the bricks and hence seeing size from only
one brick.
I think this patch fixes the problem:
http://review.gluster.org/8990
It seems that there are some other xattrs visible from client side. I've
identified 'trusted.glusterfs.quota.*.contri'. Are there any other
xattrs that I should handle on the client side ?
It seems that there's also a 'trusted.glusterfs.quota.dirty' and
'trusted.glusterfs.quota.limit-set'.
How I should handle visible xattrs in ec xlator if they have different
values in each brick ?
trusted.glusterfs.quota.size is handled by choosing the maximum value.
Thanks,
Xavi
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
