Bug 764498 (GLUSTER-2766) - Quota: nfs-server.vol showing the same quota limits for all volumes as for striped volumes
Summary: Quota: nfs-server.vol showing the same quota limits for all volumes as for st...
Keywords:
Status: CLOSED DUPLICATE of bug 764735
Alias: GLUSTER-2766
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Junaid
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-15 08:41 UTC by Saurabh
Modified: 2013-08-06 22:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: nfs
Documentation: DNR
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Saurabh 2011-04-15 08:41:29 UTC
The nfs-server.vol is displaying the same information for limit-set as for the striped volume, i.e. ds2.

and dist-rep/distribute are also showing same i.e. dr2/dist4 respectively.

Though the list command works properly.

If one disables quota on the striped volumes and limit set for other volumes is shown correctly.

But again enabling and setting values throws the same issue.

The fuse vol is fine.

######################################################################
volume ds2-quota
    type features/quota
    option limit-set /d1:1MB,/d1/dd1:500KB,/d2/dd2:500KB,/d3:1MB,/d3/dd3:500KB,/d4/dd4:500KB,/d4:500Kb
    option timeout 0
    subvolumes ds2-stripe-0
end-volume

volume dr2-quota
    type features/quota
    option limit-set /d1:1MB,/d1/dd1:500KB,/d2/dd2:500KB,/d3:1MB,/d3/dd3:500KB,/d4/dd4:500KB,/d4:500Kb
    option timeout 0
    subvolumes dr2-dht
end-volume

volume dist4-quota
    type features/quota
    option timeout 0
    option limit-set /d1:1MB,/d1/dd1:500KB,/d2/dd2:500KB,/d3:1MB,/d3/dd3:500KB,/d4/dd4:500KB,/d4:500Kb
    subvolumes dist4-dht
end-volume
###############################################################################

[root@centos-qa-client-2 sbin]# ./gluster volume quota ds2 list
	path		  limit_set	     size
----------------------------------------------------------------------------------
/d1                     1048576               131072
/d1/dd1                  512000               131072
/d2/dd2                   500KB
/d3                     1048576               131072
/d3/dd3                   500KB
/d4/dd4                   500KB
/d4                      512000               171072
[root@centos-qa-client-2 sbin]# ./gluster volume quota dr2 list
	path		  limit_set	     size
----------------------------------------------------------------------------------
/d1                  5368709120              1024000
/                    12884901888              1024000
[root@centos-qa-client-2 sbin]# ./gluster volume quota dist4 list
quota limit not set

Comment 1 Saurabh 2011-04-18 05:24:07 UTC
volume drep-quota
    type features/quota
    option timeout 0
    option limit-set /:1MB
    subvolumes drep-dht
end-volume

volume dist5-quota
    type features/quota
    option limit-set /:1MB
    option timeout 0
    subvolumes dist5-dht
end-volume


whereas,


[root@centos-qa-client-2 sbin]# ./gluster volume info drep

Volume Name: drep
Type: Distributed-Replicate
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.1.12.134:/mnt/drep
Brick2: 10.1.12.135:/mnt/ddrep
Brick3: 10.1.12.135:/mnt/drep
Brick4: 10.1.12.134:/mnt/ddrep
Options Reconfigured:
features.quota: on
[root@centos-qa-client-2 sbin]# ./gluster volume info dist5

Volume Name: dist5
Type: Distribute
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 10.1.12.134:/mnt/dist5
Brick2: 10.1.12.135:/mnt/dist5
Options Reconfigured:
features.limit-usage: /:1MB
features.quota: on
[root@centos-qa-client-2 sbin]#

Comment 2 Raghavendra G 2011-04-19 09:07:56 UTC
Have we tested this again with latest QA release? This is because there are some patches related to fixing stripe issues have gone in.

regards,
Raghavendra.

Comment 3 Junaid 2011-06-08 08:37:23 UTC

*** This bug has been marked as a duplicate of bug 3003 ***


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