I've noticed a difference in the trusted.glusterfs.quota.size field. I
am using this field instead of the quota list command because it's super
fast and doesn't hang occasionally like the command can.
In 3.6 it looks like this:
trusted.glusterfs.quota.size=0x0000000000000000
In 3.7 it looks like this:
trusted.glusterfs.quota.size=0x000000000000000000000000000000000000000000000003
I dumped these fields with:
getfattr -d -m . -e hex /mnt/brick1
The field in 3.6 is easy to decode as a hex number. In 3.7 however the
field appears to be too long or base64 encoded. Does anyone know what
happened here?
-Chris
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
