Bug 1103971
| Summary: | quota: setting limit to 16384PB shows wrong stat with list commands | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Saurabh <saujain> | |
| Component: | quota | Assignee: | Vijaikumar Mallikarjuna <vmallika> | |
| Status: | CLOSED ERRATA | QA Contact: | Anil Shah <ashah> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | low | |||
| Version: | rhgs-3.0 | CC: | annair, bmohanra, mzywusko, nsathyan, rhs-bugs, smohan, storage-qa-internal, vagarwal, vbellur, vmallika | |
| Target Milestone: | --- | |||
| Target Release: | RHGS 3.1.0 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | gluster-3.7.0-2.el6rhs | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, when a quota limit of 16384PB was set, the “quota list” output for “Soft-limit exceeded” and “Hard-limit exceeded” values was wrongly reported as “Yes”. With this fix, the supported quota limit range is changed to (0 - 9223372036854775807) and the quota list provides the correct output.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1206432 (view as bug list) | Environment: | ||
| Last Closed: | 2015-07-29 04:32:16 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: | 1206432 | |||
| Bug Blocks: | 1101270, 1202842, 1212791, 1223636 | |||
Patch submitted upstream: http://review.gluster.org/#/c/10022/ [root@darkknight ~]# gluster v quota vol0 limit-usage / 16386PB
volume quota : success
[root@darkknight ~]# gluster v quota vol0 list
Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded?
---------------------------------------------------------------------------------------------------------------------------
/ 2.0PB 80% 0Bytes 2.0PB No No
[root@darkknight ~]# gluster v quota vol0 limit-usage / 9223372036854775807
volume quota : success
[root@darkknight ~]# gluster v quota vol0 list
Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded?
---------------------------------------------------------------------------------------------------------------------------
/ 8192.0PB 80% 0Bytes 8192.0PB No No
Bugs successfully verified on build glusterfs 3.7.0 .
Hence marking this bug as verified.
Hi Vijai, The doc text is updated. Please review the same and share your technical review comments. If it looks ok, then sign-off on the same. Regards, Bhavana Doc-Text looks good to me Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html |
Description of problem: The quota limit used to setting the quota on any directory. This time I used it to set the limit of 16384PB and subsequently used the "quota list" command to collect stats related to quota. Found it out that it said "Soft-limit exceeded and Hard-limit exceeded" is said to be "Yes" whereas it should be "No" Version-Release number of selected component (if applicable): glusterfs-3.6.0.11-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. create a 6x2 volume, start it 2. enable quota 3. set quota limit of 16384PB 4. execute the quota list command Actual results: the quota list result, [root@nfs1 ~]# gluster volume quota dist-rep1 limit-usage / 16384PB volume quota : success [root@nfs1 ~]# [root@nfs1 ~]# [root@nfs1 ~]# [root@nfs1 ~]# gluster volume quota dist-rep1 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 0Bytes 80% 0Bytes 0Bytes Yes Yes Expected results: it should say Hard-limit set as 16384B and "No" "No" for Soft-limit exceeded? and Hard-limit exceeded? Additional info: