Description of problem: root@Dagobah:~# gluster volume quota vol limit-usage / 100MB limit set on / root@Dagobah:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda5 46G 25G 20G 57% / none 1.9G 732K 1.9G 1% /dev none 1.9G 2.9M 1.9G 1% /dev/shm none 1.9G 396K 1.9G 1% /var/run none 1.9G 0 1.9G 0% /var/lock /dev/sda9 37G 24G 13G 66% /misc /dev/sda6 38G 27G 11G 72% /muzic /dev/sda8 38G 36G 1.4G 97% /myst /dev/sda7 94G 67G 27G 72% /tent dagobah:vol 100M -43G 43G - /root/mount dagobah:vol 100M -43G 43G - /root/newmount root@Dagobah:~# gluster volume quota vol list path limit_set size ------------------------------------------------------------------------------- / 100MB 208.1MB Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Did you set the limit on a directory already containing data? If it is so, this is not a bug, since quota is enforced only for operations done after a limit is set. If not, please provide exact test cases. regards, Raghavendra.
Sorry, I misread the bug. But anyways, answers to the questions asked are welcome.
*** Bug 773528 has been marked as a duplicate of this bug. ***
CHANGE: http://review.gluster.com/3102 (features/quota: don't adjust statfs buffer if size used is already greater than available limit.) merged in master by Vijay Bellur (vijay)
negative values are not seen anymore