Currently below mentioned bugs are marked as known issues. Actually they are expected behavior of quota. Bug# 1026371 - quota: Soft limit alert not triggered after increasing quota size and even after modifying soft-limit %age Bug# 1023120 - Appending data to a file using Vi editor violates quota limits Bug# 1020275 - quota: Exceeding upto 100% of the hard limit on file creation with different sizes and quota limit is less than 2GB. Bug# 1019752 - [Quota] quota fails generate alerts on the slave in a geo-rep setup even after slave has crossed soft-limit Bug# 1116121 - Quota: Soft limits are not triggered when the hard limit is exceeded. Bug# 1116115 - Quota: Smaller limits getting crossed by as much as 300% Bug# 999458 - quota: limit gets crossed for small values of "hard limit" setting Bug# 1001548 - quota: disk quota was set to 1.0GB but could create a file of 1.4GB from mount. Here is the behavior of quota: If the rate of I/O is more than the value of hard-timeout and soft-timeout, there is possibility of quota limit being exceeded For example: If the rate of IO is 1GB/sec If hard-timeout is set to 5sec (default value). If soft-timeout is set to 60sec (default value). Then we may exceed quota limit by ~30GB - 60GB In order to attain a strict checking of quota limit, then you need to lower the value of hard-timeout and soft-timeout Command to set timeout: gluster volume quota <volume-name> soft-timeout 0 gluster volume quota <volume-name> hard-timeout 0
Hi Vijai, I found that the information suggested by you is already present in the Admin guide that is added as a note under section 13.5. https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/ch13s05.html Based on our discussion this information is sufficient and hence closing this bug.