Bug 764484 (GLUSTER-2752)

Summary:	Quota: for setting limit, it's not allowing values with decimal point
Product:	[Community] GlusterFS	Reporter:	Saurabh <saurabh>
Component:	quota	Assignee:	Raghavendra G <raghavendra>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	amarts, gluster-bugs
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 Saurabh 2011-04-14 06:42:47 UTC

[root@centos-qa-client-2 sbin]# ./gluster volume quota dist-rep2 limit-usage / 2.5MB
Please enter a correct value
Usage: volume quota <VOLNAME> <enable|disable|limit-usage|list|remove> [path] [value]
[root@centos-qa-client-2 sbin]# ./gluster volume quota dist-rep2 limit-usage / 2MB
limit set on /

Comment 1 Raghavendra G 2011-04-19 09:06:18 UTC

This is due to the way gf_string2bytesize is implemented. It does not take floating point sizes. Not fixing this for 3.2.0

Comment 2 Amar Tumballi 2011-04-25 09:27:48 UTC

Lets not fix this as gf_string2bytesize is the function called from many places (for example, for 'cache-size' in io-cache). for 2.5MB one can give '2560KB'.

We can specify this as an known issue in documentation and tell users to use complete numbers.