Bug 1070623 - Gluster Quotas implementation issue
Summary: Gluster Quotas implementation issue
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-27 09:39 UTC by gaddam.bharath23
Modified: 2015-10-28 06:02 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-28 06:02:49 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:
mselvaga: needinfo+


Attachments (Terms of Use)

Description gaddam.bharath23 2014-02-27 09:39:12 UTC
set the usage list using the following command

gluster volume quota testfs01 limit-usage /bharath 100MB

It also lists the same on the volume info command output as attached
~]# gluster volume info

Volume Name: gv0
Type: Replicate
Volume ID: 1b4b227f-656d-4d67-9b83-41e4da8aa2e5
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 10.15.0.134:/export/sdb1/brick
Brick2: 10.15.0.135:/export/sdb1/brick
Options Reconfigured:
features.limit-usage: /bharath:100MB
features.quota: on
features.read-only: off
auth.reject: none

We were able to list the gluster volume usage 

[root@Func-l83 bharath]# gluster volume quota gv0 list
        path              limit_set          size
----------------------------------------------------------------------------------
/bharath                  100MB              148.9MB

After which we had copied some data on the specified directory, but the quota does not restrict copying data.

Comment 1 Manikandan 2015-10-20 06:52:18 UTC
Hi,
Did you set the soft/hard timeout to zero ?

volume quota <VOLNAME> {alert-time|soft-timeout|hard-timeout} {<time>}

Refer here : https://gluster.readthedocs.org/en/latest/Administrator%20Guide/Directory%20Quota/


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