Bug 764597 (GLUSTER-2865)

Summary:	[Engineering Consult] Glusterfs 3.2 Volume Quota Feature
Product:	[Community] GlusterFS	Reporter:	Mark Brooke <mark>
Component:	core	Assignee:	Anand Avati <aavati>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	urgent
Version:	3.1.0	CC:	amarts, chrisw, gluster-bugs, renee
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Mark Brooke 2011-04-29 23:19:15 UTC

Wondering if this is expected behavior of Quota.

I create a 500MB quota to path /mnt/reptest

*Set Quota to 500MB:
>[root@n01 mnt]# gluster volume quota reptest2 limit-usage /mnt/reptest 500MB
>limit set on /mnt/reptest

Cannot perform quota list to verify being set, filed bug 764596.

*Create 1.1GB File in /mnt/reptest:
>[root@n01 reptest]# dd if=/dev/zero of=bigfile bs=1M count=1024
>1024+0 records in
>1024+0 records out
>1073741824 bytes (1.1 GB) copied, 18.5866 seconds, 57.8 MB/s
>[root@n01 reptest]# ll
>total 1049608
>-rw-r--r-- 1 root root 1073741824 Apr 29 15:42 bigfile

*Create 'test1' directory under /mnt/reptest and create 4MB file:
>[root@n01 reptest]# mkdir test1
>[root@n01 reptest]# cd test1
>[root@n01 test1]# dd if=/dev/zero of=bigfile bs=4k count=1024
>1024+0 records in
>1024+0 records out
>4194304 bytes (4.2 MB) copied, 0.021502 seconds, 195 MB/s
>[root@n01 test1]# ll
>total 4104
>-rw-r--r-- 1 root root 4194304 Apr 29 15:44 bigfile

*Create 'test2' directory under /mnt/reptest and create 4MB file:
>[root@n01 reptest]# mkdir test2
>[root@n01 reptest]# cd test2
>[root@n01 test2]# dd if=/dev/zero of=bigfile bs=4k count=1024
>1024+0 records in
>1024+0 records out
>4194304 bytes (4.2 MB) copied, 0.057049 seconds, 73.5 MB/s
>[root@n01 test2]# ll
>total 4104
>-rw-r--r-- 1 root root 4194304 Apr 29 15:45 bigfile

*Create 'test3' directory under /mnt/reptest and create 4MB file:
>[root@n01 reptest]# mkdir test3
>[root@n01 reptest]# cd test3
>[root@n01 test3]# dd if=/dev/zero of=bigfile bs=4k count=1024
>1024+0 records in
>1024+0 records out
>4194304 bytes (4.2 MB) copied, 0.025944 seconds, 162 MB/s
>[root@n01 test3]# ll
>total 4104
>-rw-r--r-- 1 root root 4194304 Apr 29 15:45 bigfile


All file transfers were complete, nothing in-transit, not known if allowing one file to be created within new directory is due to concerns about data left in cache - not flushed yet. Is this expected behavior? Please advise.

Thank you,
Mark

Comment 1 Amar Tumballi 2011-05-01 13:24:28 UTC

Hi Mark,

Sorry for making it not very clear in documentation or in training. All quota paths you set are relative path to the volume. Ie, if you set quota limit on '/mnt/glusterfs' in a 'test-volume' then if you mount 'test-volume' on client in /mnt/glusterfs/, actually, quota limit will be set on '/mnt/glusterfs/mnt/glusterfs' and not on the mount point itself. If you want to set the quota limit to whole volume, please use '/' as the path for setting the limit.

Please confirm if it works, so we can close the bug.

Comment 2 Mark Brooke 2011-05-02 15:14:05 UTC

Hi Amar,

Thank you for the information. I'm still not very clear on this.

1). I have a replicated volume named 'rep1' and the bricks are set to: 192.168.111.129:/rep1 & 192.168.111.139:/rep1.

2). After starting the volume I set the quota as 'gluster volume quota rep1 limit-usage /mnt/quotatest 100MB (based on what's documented and your comments) The quota comes back 'as set' yet I still cannot list the quota.

3). Can you please tell me how I can list the quota for /rep1/mnt/quotatest?


Mark

Comment 3 Mark Brooke 2011-05-02 15:18:28 UTC

Additional Information on rep1 volume:

Volume Name: rep1
Type: Replicate
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 192.168.111.129:/mnt/rep1
Brick2: 192.168.111.139:/mnt/rep1
Options Reconfigured:
features.limit-usage: /mnt/quotatest:100MB <--
features.quota: on

[root@n01 mnt]# gluster volume quota rep1 list /mnt/quotatest
[root@n01 mnt]#

Comment 4 Mark Brooke 2011-05-02 16:07:47 UTC

Amar,

You can close this bug. With Harsha's help it was determined that:

1). I was using NFS mount (not glusterfs) which doesn't support extended attributes.

2). Directories were created on the back-end.

It's a lot more clear to me now.

Thank you,
Mark