Red Hat Bugzilla – Bug 974025
quota: limits gets crossed by 25%
Last modified: 2016-01-19 01:12:10 EST
Description of problem:
The volume created is 6x2,
[root@nfs2 ~]# gluster volume info
Volume Name: dit-rep
Volume ID: 9f0499fd-39c1-4c94-8d47-b767d6cccf86
Number of Bricks: 6 x 2 = 12
I recieve "Disk quota exceeded" on stdout, but actually after a while if I try again I can create new file.
Version-Release number of selected component (if applicable):
[root@nfs1 rpms]# rpm -qa | grep glusterfs
Steps to Reproduce:
1. create a volume of 6x2 volume, start it
2. enable quota
3. gluster volume quota <vol-name> limit-usage / 2GB
4. mount -t glusterfs server-ip:<vol-name> <mount-point>
5. execute in a for loop,
dd if=/dev/urandom of=f.$i bs=1024 count=1024
till "Disk quota exceeded" is thrown on the stdout
6. wait for some time, lets say 30sec.
7. give another of creating files in for loop.
8. repeat similar steps[5-6-7] quite 2-3 times.
step 7 and 8 creates more files.
I have tried to create files of 1MB in size
as per the limit set of 2GB, there should be around 2048 files in total,
but I have been able to create,
[root@rhel6 glusterfs-test]# ls | wc -l
[root@rhel6 glusterfs-test]# du -sh
In fact I am able to beyond.
from server end,
[root@nfs2 ~]# gluster volume quota dit-rep list
Path Hard-limit Soft-limit Used Available
/ 2GB 90% 415.0MB 1.6GB
the number of files created after limit is crossed is large.
The quota enforcement should be proper.
The reason being for this is that the size in the quota context was being updated in the lookup fop and removed it in the patch mentioned in the comment #5.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
For information on the advisory, and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.