Bug 1147378
| Summary: | Enabling Quota on existing data won't create pgfid xattrs | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Vijaikumar Mallikarjuna <vmallika> | |
| Component: | glusterd | Assignee: | Vijaikumar Mallikarjuna <vmallika> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | mainline | CC: | bugs, nbalacha, psriniva, rgowdapp, sharne, smohan, storage-qa-internal, vmallika | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.7.0 | Doc Type: | Known Issue | |
| Doc Text: |
Enabling the Quota feature on Red Hat Storage version 3 does not create parent GFID extended attributes on existing data. The parent GFID extended attributes are used to construct the absolute path (from the file to the volume root) for nameless lookup operations on files. As NFS heavily relies on nameless lookup operations, quota enforcement through NFS would be inconsistent if quota is enabled on a volume with existing data as the information about the parent directories is not available. This issue is not observed if quota is enabled on Red Hat Storage version 2.1 before upgrading to Red Hat Storage 3 as Red Hat Storage 2.1 creates the parent GFID extended attributes on existing data as well.
Workaround: Enable the Quota feature on Red Hat Storage version 2.1 and then upgrade to Red Hat Storage version 3.0.
|
Story Points: | --- | |
| Clone Of: | 1146830 | |||
| : | 1147953 1153900 (view as bug list) | Environment: | ||
| Last Closed: | 2015-05-14 17:27: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: | 1146830 | |||
| Bug Blocks: | 1147953, 1153900 | |||
|
Comment 1
Anand Avati
2014-09-29 07:36:55 UTC
REVIEW: http://review.gluster.org/8890 (glusterd/quota: Heal pgfid xattr on existing data when the quota is enable) posted (#1) for review on release-3.6 by Vijaikumar Mallikarjuna (vmallika) COMMIT: http://review.gluster.org/8878 committed in master by Vijay Bellur (vbellur) ------ commit f95a25c35e1ced6a3c05030d34555b757b14e1c9 Author: vmallika <vmallika> Date: Mon Sep 29 13:02:30 2014 +0530 glusterd/quota: Heal pgfid xattr on existing data when the quota is enable The pgfid extended attributes are used to construct the ancestry path (from the file to the volume root) for nameless lookups on files. As NFS relies on nameless lookups heavily, quota enforcement through NFS would be inconsistent if quota were to be enabled on a volume with existing data. Solution is to heal the pgfid extended attributes as a part of lookup perfomed by quota-crawl process. In a posix lookup check for pgfid xattr and if it is missing set the xattr. Change-Id: I5912ea96787625c496bde56d43ac9162596032e9 BUG: 1147378 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/8878 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur> Hi Vijai, I see this bug in the 3.0.3 known issues tracker bug https://bugzilla.redhat.com/show_bug.cgi?id=1153907. Can you please change the doc text field to Known Issues and add the doc text? Hi Vijai, Can you please review the edited doc text for technical accuracy and sign off? doc text looks good to me 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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |