Bug 1721462 - Quota limits not honored writes allowed past quota limit.
Summary: Quota limits not honored writes allowed past quota limit.
Keywords:
Status: NEW
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: hari gowtham
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-18 10:59 UTC by Kshithij Iyer
Modified: 2019-08-31 18:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Kshithij Iyer 2019-06-18 10:59:44 UTC
Description of problem:
On a six node cluster created a distributed-replicated enabled quota set hard and soft time out to zero. Created files and directories from mount such that the limit is reached. Performed an add-brick and started rebalance after which we killed one of the bricks and started the volume while rebalance and self heal is in progress.Created some files and directories write allowed past quota limit.

Version-Release number of selected component (if applicable):
Whatever is the latest version in upstream

How reproducible:
constantly

Steps to Reproduce:
1.Enable quota on the volume.
2.Set hard and soft time out to zero.
3.Create some files and directories from mount point so that the limits are reached.
4.Perform add-brick operation on the volume. 
5.Start rebalance on the volume. 
6.While rebalance is running, kill one of the bricks of the volume and start after a while. 
7.While rebalance + self heal is in progress.
8.Create some more files and directories from the mount point until limit is hit.

Actual results:
Writes allowed past quota limit.

Expected results:
Writes shouldn't be allowed past quota limit.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.