Bug 1002885
Summary: | Quota limit violated upon creating a file after add-brick and fix-layout | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | shylesh <shmohan> |
Component: | glusterfs | Assignee: | vpshastry <vshastry> |
Status: | CLOSED ERRATA | QA Contact: | shylesh <shmohan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | amarts, asriram, grajaiya, kparthas, nsathyan, rhs-bugs, sdharane, senaik, surs, vbellur |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0.38rhs | Doc Type: | Bug Fix |
Doc Text: |
Previously, the quota limit configuration stored in the extended attributes of the directory would not be present in the newly added brick. The quota list command may fail to list the limits on the directory when only the newly added bricks are available. Now, with this update, the configuration is copied on the newly added bricks and the quota list command does not fail.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-27 15:35: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: | |||
Bug Blocks: | 957769, 1003549 |
Description
shylesh
2013-08-30 07:22:09 UTC
(https://code.engineering.redhat.com/gerrit/#/c/12366/) and https://code.engineering.redhat.com/gerrit/#/c/12397/ have been submitted for review. Per bug triage 10/17. *** Bug 1021949 has been marked as a duplicate of this bug. *** verified on 3.4.0.43rhs-1.el6rhs.x86_64. Now adding a brick properly heals quota xattrs thus quota is preserved. 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. http://rhn.redhat.com/errata/RHBA-2013-1769.html |