Bug 1104692 - quota: setting the limit fails
Summary: quota: setting the limit fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Nagaprasad Sathyanarayana
QA Contact:
URL:
Whiteboard:
Depends On: 1103688
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-04 13:53 UTC by vpshastry
Modified: 2016-02-18 00:20 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1103688
Environment:
Last Closed: 2014-11-11 08:34:13 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description vpshastry 2014-06-04 13:53:30 UTC
Description of problem:
I tried to set the limit for quota and it failed, seen on the latest build.


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.

Comment 1 Anand Avati 2014-06-04 13:55:05 UTC
REVIEW: http://review.gluster.org/7967 (features/quota: No root squash for quota aux mount by default) posted (#2) for review on master by Varun Shastry (vshastry)

Comment 2 Anand Avati 2014-06-05 07:19:45 UTC
REVIEW: http://review.gluster.org/7967 (features/quota: No root squash for quota aux mount by default) posted (#3) for review on master by Varun Shastry (vshastry)

Comment 3 Anand Avati 2014-06-12 07:13:08 UTC
REVIEW: http://review.gluster.org/7967 (features/quota: No root squash for quota aux mount by default) posted (#4) for review on master by Varun Shastry (vshastry)

Comment 4 Anand Avati 2014-06-16 06:12:58 UTC
COMMIT: http://review.gluster.org/7967 committed in master by Raghavendra G (rgowdapp) 
------
commit 47230eb38d96e51d2d5e976eda7ff82c62f6eedd
Author: Varun Shastry <vshastry>
Date:   Wed Jun 4 12:43:18 2014 +0530

    features/quota: No root squash for quota aux mount by default
    
    With change 28209283a67f13802cc0c1d3df07c676926810a2, the root squash option
    is enabled by default even for the trusted clients. This disallowed quota
    auxiliary mount from setting the limit.
    
    This patch adds the quota aux mount process to list of 'special' clients which
    have the root squash disabled by default.
    
    Change-Id: Ie6583dd3deb170563daf001239c51bcff1ce078b
    BUG: 1104692
    Signed-off-by: Varun Shastry <vshastry>
    Reviewed-on: http://review.gluster.org/7967
    Reviewed-by: Krutika Dhananjay <kdhananj>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>
    Tested-by: Raghavendra G <rgowdapp>

Comment 7 Niels de Vos 2014-09-22 12:41:56 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 8 Niels de Vos 2014-11-11 08:34:13 UTC
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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


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