Bug 1103688 - quota: setting the limit fails
Summary: quota: setting the limit fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: quota
Version: rhgs-3.0
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: RHGS 3.0.0
Assignee: Nagaprasad Sathyanarayana
QA Contact: Saurabh
URL:
Whiteboard:
Depends On:
Blocks: 1104692
TreeView+ depends on / blocked
 
Reported: 2014-06-02 11:19 UTC by Saurabh
Modified: 2016-09-17 12:37 UTC (History)
8 users (show)

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.
Clone Of:
: 1104692 (view as bug list)
Environment:
Last Closed: 2014-09-22 19:40:12 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:1278 0 normal SHIPPED_LIVE Red Hat Storage Server 3.0 bug fix and enhancement update 2014-09-22 23:26:55 UTC

Description Saurabh 2014-06-02 11:19:37 UTC
Description of problem:
I tried to set the limit for quota and it failed, seen on the latest build.

Version-Release number of selected component (if applicable):
glusterfs-3.6.0.11-1.el6rhs.x86_64

How reproducible:
always

Steps to Reproduce:
1. create a volume of 6x2 type, start it
2. volume set root-squash on, server-anonuid, server-anongid, 
3. enable quota
4. try to set the limit for quota

Actual results:
step  4 fails,
[root@nfs1 ~]# gluster volume quota dist-rep limit-usage / 10GB
quota command failed : setxattr of 'trusted.glusterfs.quota.limit-set' failed on /var/run/gluster/dist-rep/. Reason : Permission denied


[root@nfs1 ~]# gluster volume info dist-rep
 
Volume Name: dist-rep
Type: Distributed-Replicate
Volume ID: 479f93d9-ed9b-4097-8d95-7a0657ee912f
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.root-squash: on
server.anonuid: 502
server.anongid: 501
features.quota: on


Expected results:
setting the limit for quota should work.

Additional info:

Comment 3 Dusmant 2014-06-16 09:45:36 UTC
Marking it as blocker, after discussing with Alok and Vivek...

Comment 4 vpshastry 2014-06-17 09:45:01 UTC
The patch is submitted at https://code.engineering.redhat.com/gerrit/27014 and merged.

Comment 5 Saurabh 2014-06-19 11:19:06 UTC
[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

Comment 6 Pavithra 2014-07-23 06:29:27 UTC
Hi Varun, 

Can you please review the edit doc text for technical accuracy and sign off?

Comment 7 vpshastry 2014-07-24 07:16:16 UTC
Pavithra, the doc text seems perfect.

Comment 10 errata-xmlrpc 2014-09-22 19:40:12 UTC
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


Note You need to log in before you can comment on or make changes to this bug.