Back to bug 1020275

Who When What Removed Added
Gowrishankar Rajaiyan 2013-10-18 12:31:10 UTC Keywords ZStream
CC grajaiya
Gowrishankar Rajaiyan 2013-10-23 10:36:34 UTC Summary quota: Exceeding more than 20 % of the hard limit on file creation with different sizes quota: Exceeding upto 100% of the hard limit on file creation with different sizes
Vivek Agarwal 2013-10-24 03:23:05 UTC Priority unspecified medium
CC vagarwal
Pavithra 2013-10-25 10:24:22 UTC Blocks 1020127
Gowrishankar Rajaiyan 2013-11-11 08:16:07 UTC Summary quota: Exceeding upto 100% of the hard limit on file creation with different sizes quota: Exceeding upto 100% of the hard limit on file creation with different sizes and quota limit is less than 2GB.
Susant Kumar Palai 2013-11-11 14:05:54 UTC CC spalai
Vivek Agarwal 2013-11-12 10:37:12 UTC Doc Type Bug Fix Known Issue
Red Hat Bugzilla 2013-11-12 10:37:12 UTC Doc Type Known Issue Bug Fix
Vivek Agarwal 2013-11-14 11:26:58 UTC CC asriram, gluster-bugs, mhideo, storage-doc, vraman
Component glusterfs-server doc-Release_Notes
Assignee rhs-bugs psriniva
Pavithra 2013-11-25 07:02:13 UTC Doc Text Cause: x

Consequence:

Workaround (if any):

Result:
Doc Type Bug Fix Known Issue
Pavithra 2013-11-25 07:04:48 UTC Doc Text Cause: x

Consequence:

Workaround (if any):

Result:
Creating files of different sizes leads to the violation of the quota hard limit.
Vivek Agarwal 2013-12-03 07:35:24 UTC Component doc-Release_Notes glusterfs
Vivek Agarwal 2013-12-03 08:24:25 UTC Assignee psriniva spalai
krishnan parthasarathi 2014-02-28 09:44:32 UTC Component glusterfs gluster-quota
John Skeoch 2014-03-31 01:32:33 UTC CC vraman rwheeler
Sudhir D 2014-08-22 09:23:15 UTC QA Contact sdharane storage-qa-internal
Vijaikumar Mallikarjuna 2015-01-12 13:37:22 UTC Status NEW CLOSED
CC vmallika
Resolution --- WONTFIX
Doc Text Creating files of different sizes leads to the violation of the quota hard limit.
Last Closed 2015-01-12 08:37:22 UTC
Red Hat Bugzilla 2015-01-12 13:37:22 UTC Doc Type Known Issue Bug Fix
Vijaikumar Mallikarjuna 2015-01-12 13:37:50 UTC Doc Text When the quota hard-timeout is set to default value of 30,
the quota limit is checked once in 30 seconds and during
that 30 second time window there is possibility of quota
hard-limit being exceeded. In order to attain a strict
checking of quota limit it is recommended to set the
quota soft-timeout and hard-timeout to lower value so
that quota limit is checked frequently, and possibility of
quota hard-limit being exceeded is reduced.
Doc Type Bug Fix Known Issue
Vijaikumar Mallikarjuna 2015-01-15 07:13:09 UTC Status CLOSED NEW
Resolution WONTFIX ---
Keywords Reopened
Vijaikumar Mallikarjuna 2015-01-16 08:08:32 UTC Keywords Reopened, ZStream
Status NEW CLOSED
Depends On 1182890
Resolution --- WONTFIX
Doc Text When the quota hard-timeout is set to default value of 30,
the quota limit is checked once in 30 seconds and during
that 30 second time window there is possibility of quota
hard-limit being exceeded. In order to attain a strict
checking of quota limit it is recommended to set the
quota soft-timeout and hard-timeout to lower value so
that quota limit is checked frequently, and possibility of
quota hard-limit being exceeded is reduced.
Expected 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
Last Closed 2015-01-12 08:37:22 UTC 2015-01-16 03:08:32 UTC
Pavithra 2015-01-16 08:37:05 UTC Depends On 1182921
Rejy M Cyriac 2016-09-17 12:38:21 UTC CC rhs-bugs, storage-qa-internal
Component gluster-quota quota

Back to bug 1020275