Bug 1261404

Summary:	No quota API to get real hard-limit value.
Product:	[Community] GlusterFS	Reporter:	Manikandan <mselvaga>
Component:	quota	Assignee:	Manikandan <mselvaga>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs, mselvaga, smohan, vnosov
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1250735
Clones:	1263075 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:35:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1250735, 1267817
Bug Blocks:	1263075

Description Manikandan 2015-09-09 09:09:32 UTC

+++ This bug was initially created as a clone of Bug #1250735 +++

Description of problem: The quota list command returns rounded hard-limit value. If it is rounded it could not be used to restore the quota configuration settings. For example, the hard-limit is set 3080MB, but the quota list returns 3.0GB as a hard-limit value. User has to maintain its own records about true hard-limit values or to use getfattr to check extended attributes.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2015-09-09 09:17:57 UTC

REVIEW: http://review.gluster.org/12137 (quota : xml output modified to give exact available space in bytes) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)

Comment 2 Vijay Bellur 2015-09-09 14:42:53 UTC

REVIEW: http://review.gluster.org/12137 (quota : xml output modified to give exact available space in bytes) posted (#2) for review on master by Manikandan Selvaganesh (mselvaga)

Comment 3 Vijay Bellur 2015-09-10 05:40:17 UTC

REVIEW: http://review.gluster.org/12137 (quota : xml output modified to give exact available space in bytes.) posted (#3) for review on master by Manikandan Selvaganesh (mselvaga)

Comment 4 Vijay Bellur 2015-09-10 09:14:32 UTC

REVIEW: http://review.gluster.org/12137 (quota : xml output modified to give exact available space in bytes) posted (#4) for review on master by Manikandan Selvaganesh (mselvaga)

Comment 5 Vijay Bellur 2015-09-11 13:20:39 UTC

REVIEW: http://review.gluster.org/12137 (quota : xml output modified to give exact available space in bytes) posted (#5) for review on master by Manikandan Selvaganesh (mselvaga)

Comment 6 Vijay Bellur 2015-09-15 11:54:39 UTC

REVIEW: http://review.gluster.org/12137 (quota : xml output modified to give exact available space in bytes) posted (#6) for review on master by Manikandan Selvaganesh (mselvaga)

Comment 7 Niels de Vos 2016-06-16 13:35:52 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user