Bug 1549482
Summary: | Quota: After deleting directory from mount point on which quota was configured, quota list command output is blank | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | hari gowtham <hgowtham> |
Component: | quota | Assignee: | hari gowtham <hgowtham> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.10 | CC: | amukherj, ashah, bugs, redhat.bugs, rhs-bugs, storage-qa-internal, sunnikri |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.10.11 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1418259 | Environment: | |
Last Closed: | 2018-03-10 12:37:56 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: | 1418259 | ||
Bug Blocks: | 1418227 |
Comment 1
Worker Ant
2018-02-27 08:56:34 UTC
COMMIT: https://review.gluster.org/19637 committed in release-3.10 by "Shyamsundar Ranganathan" <srangana> with a commit message- Fixes quota list when stale gfid exist in quota.conf when an rmdir is done, the gfid corresponding to the dir remains in quota.conf (if a limit was configured on the dir). The quota list should ignore them and print the remaining limits. In case the last gfid in quota.conf happened to be stale, the print code was getting skipped. Refactored the code to ensure printing happens. >Change-Id: I3ac8e8a7a62d34e1fa8fd2734419459112c71797 >BUG: 1418259 >Signed-off-by: Sanoj Unnikrishnan <sunnikri> >Reviewed-on: https://review.gluster.org/16507 >Smoke: Gluster Build System <jenkins.org> >NetBSD-regression: NetBSD Build System <jenkins.org> >CentOS-regression: Gluster Build System <jenkins.org> >Reviewed-by: Manikandan Selvaganesh <manikandancs333> >Reviewed-by: Raghavendra G <rgowdapp> Change-Id: I3ac8e8a7a62d34e1fa8fd2734419459112c71797 BUG: 1549482 Signed-off-by: Hari Gowtham <hgowtham> 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.10.11, please open a new bug report. glusterfs-3.10.11 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://lists.gluster.org/pipermail/announce/2018-March/000091.html [2] https://www.gluster.org/pipermail/gluster-users/ |