Bug 1103688
| Summary: | quota: setting the limit fails | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Saurabh <saujain> | |
| Component: | quota | Assignee: | Nagaprasad Sathyanarayana <nsathyan> | |
| Status: | CLOSED ERRATA | QA Contact: | Saurabh <saujain> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | rhgs-3.0 | CC: | dpati, mzywusko, nsathyan, psriniva, rhs-bugs, smohan, ssamanta, storage-qa-internal | |
| Target Milestone: | --- | |||
| Target Release: | RHGS 3.0.0 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.6.0.19-1 | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the user could not set or configure the quota limits as the root squash feature blacklisted the glusterd client used to configure the quota limits on a brick. With this fix, the glusterd client is added to a white-list of the root-squash exception list. As a result, quota limit can be be set without any issue.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1104692 (view as bug list) | Environment: | ||
| Last Closed: | 2014-09-22 19:40:12 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: | 1104692 | |||
|
Description
Saurabh
2014-06-02 11:19:37 UTC
Marking it as blocker, after discussing with Alok and Vivek... The patch is submitted at https://code.engineering.redhat.com/gerrit/27014 and merged. [root@nfs1 ~]# gluster volume set dist-rep root-squash on
volume set: success
[root@nfs1 ~]# gluster volume set dist-rep server.anonuid 502
volume set: success
[root@nfs1 ~]# gluster volume set dist-rep server.anongid 501
volume set: success
[root@nfs1 ~]# gluster volume info dist-rep
Volume Name: dist-rep
Type: Distributed-Replicate
Volume ID: 98fb382d-a5ca-4cb6-bde1-579608485527
Status: Started
Snap Volume: no
Number of Bricks: 6 x 2 = 12
Transport-type: tcp
Bricks:
Brick1: 10.70.37.62:/bricks/d1r1
Brick2: 10.70.37.215:/bricks/d1r2
Brick3: 10.70.37.44:/bricks/d2r1
Brick4: 10.70.37.201:/bricks/d2r2
Brick5: 10.70.37.62:/bricks/d3r1
Brick6: 10.70.37.215:/bricks/d3r2
Brick7: 10.70.37.44:/bricks/d4r1
Brick8: 10.70.37.201:/bricks/d4r2
Brick9: 10.70.37.62:/bricks/d5r1
Brick10: 10.70.37.215:/bricks/d5r2
Brick11: 10.70.37.44:/bricks/d6r1
Brick12: 10.70.37.201:/bricks/d6r2
Options Reconfigured:
server.anongid: 501
server.anonuid: 502
server.root-squash: on
nfs.addr-namelookup: on
nfs.rpc-auth-reject: 10.70.35.33
features.quota-deem-statfs: on
features.quota: on
performance.readdir-ahead: on
snap-max-hard-limit: 256
snap-max-soft-limit: 90
auto-delete: disable
[root@nfs1 ~]#
[root@nfs1 ~]#
[root@nfs1 ~]#
[root@nfs1 ~]# gluster volume quota dist-rep list
quota: No quota configured on volume dist-rep
[root@nfs1 ~]# gluster volume quota dist-rep limit-usage / 250GB
volume quota : success
[root@nfs1 ~]# gluster volume quota dist-rep list
Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded?
---------------------------------------------------------------------------------------------------------------------------
/ 250.0GB 80% 5.0GB 245.0GB No No
Hence, moving the BZ to verified
Hi Varun, Can you please review the edit doc text for technical accuracy and sign off? Pavithra, the doc text seems perfect. 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/RHEA-2014-1278.html |