I have a distributed volume with quota's enabled:
Volume Name: storage
Type: Distribute
Volume ID: 26d355cb-c486-481f-ac16-e25390e73775
Status: Started
Number of Bricks: 4
Transport-type: tcp
Bricks:
Brick1: 10.0.231.50:/mnt/raid6-storage/storage
Brick2: 10.0.231.51:/mnt/raid6-storage/storage
Brick3: 10.0.231.52:/mnt/raid6-storage/storage
Brick4: 10.0.231.53:/mnt/raid6-storage/storage
Options Reconfigured:
performance.cache-size: 1GB
performance.readdir-ahead: on
features.quota: on
diagnostics.brick-log-level: WARNING
Here is a partial list of quotas:
# /usr/sbin/gluster volume quota storage list
Path Hard-limit Soft-limit Used
Available Soft-limit exceeded? Hard-limit exceeded?
---------------------------------------------------------------------------------------------------------------------------
...
/projects-CanSISE 10.0TB 80% 11.9TB
0Bytes Yes Yes
...
If I du on that location I do not get 11.9TB of space used (fuse mount point):
[root@storage projects-CanSISE]# du -hs
9.5T .
Can someone provide an explanation for how the quota mechanism tracks
disk usage? How often does the quota mechanism check its accuracy? And
how could it get so far off?
Can I get gluster to rescan that location and update the quota usage?
Thanks,
Steve
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
