Bug 1271490
| Summary: | rm -rf on /run/gluster/vol/<directory name>/ is not showing quota output header for other quota limit applied directories | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Manikandan <mselvaga> |
| Component: | quota | Assignee: | Manikandan <mselvaga> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.7.6 | CC: | bugs, gluster-bugs, kaushal, smohan |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.7.6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1269375 | Environment: | |
| Last Closed: | 2015-11-17 06:00:20 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: | 1269375 | ||
| Bug Blocks: | 1271178, 1275914 | ||
|
Description
Manikandan
2015-10-14 07:14:04 UTC
REVIEW: http://review.gluster.org/12356 (cli/quota : rm -rf on /<mountpoint>/<dir> is not showing quota header) posted (#1) for review on release-3.7 by Manikandan Selvaganesh (mselvaga) COMMIT: http://review.gluster.org/12356 committed in release-3.7 by Kaushal M (kaushal) ------ commit 0f72aa8668a6d2da4cce9cd04296454f2bc99d58 Author: Manikandan Selvaganesh <mselvaga> Date: Tue Oct 13 14:28:03 2015 +0530 cli/quota : rm -rf on /<mountpoint>/<dir> is not showing quota header Currently, when 'gluster v quota <VOLNAME> list' command is issued after an rm -rf on /run/gluster/vol/<directory>, quota output header is not shown. It is because the list_count was properly calculated with 'gluster v quota <VOLNAME> remove /path' and not with an rm -rf. The patch fixes this issue. Backport of http://review.gluster.org/#/c/12345/ Cherry-picked from commit 00eeb153f4ea473c6636147f6c72c04336128198 > Change-Id: I5266a8b0b9322b7db1b9e1d6b0327065931f4bcb > BUG: 1269375 > Signed-off-by: Manikandan Selvaganesh <mselvaga> > Reviewed-on: http://review.gluster.org/12345 > Reviewed-by: Vijaikumar Mallikarjuna <vmallika> > Tested-by: NetBSD Build System <jenkins.org> > Tested-by: Gluster Build System <jenkins.com> > Reviewed-by: Kaushal M <kaushal> Change-Id: I5266a8b0b9322b7db1b9e1d6b0327065931f4bcb BUG: 1271490 Signed-off-by: Manikandan Selvaganesh <mselvaga> Reviewed-on: http://review.gluster.org/12356 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal> 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.7.6, please open a new bug report. glusterfs-3.7.6 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://www.gluster.org/pipermail/gluster-users/2015-November/024359.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |