Description of problem: Valid error: $ gluster volume quota HadoopVol limit-usage /tmp/test2 9223372036854775807 quota command failed : Hard-limit 9223372036854775807 is greater than 9223372036854775807bytes. Please set a smaller limit. Bug: gluster volume quota HadoopVol limit-usage /tmp/test2 9223372036854775800 quota command failed : Hard-limit 9223372036854775800 is greater than 9223372036854775807bytes. Please set a smaller limit. I understand that this is just theoretical value for limit-usage so max value for limit-usage should be changed or user should be able to set it up. Version-Release number of selected component (if applicable): glusterfs-3.4.0.44rhs-1.el6rhs.x86_64 glusterfs-fuse-3.4.0.44rhs-1.el6rhs.x86_64 glusterfs-geo-replication-3.4.0.44rhs-1.el6rhs.x86_64 glusterfs-libs-3.4.0.44rhs-1.el6rhs.x86_64 glusterfs-server-3.4.0.44rhs-1.el6rhs.x86_64 python-rhsm-1.8.17-1.el6_4.x86_64 redhat-storage-logos-60.0.17-1.el6rhs.noarch rhs-hadoop-2.3.0-6.noarch rhs-hadoop-install-1_10-1.el6rhs.noarch How reproducible: 100% Actual results: It is not able to set up limit-usage to LONG.MAX - few bytes even if it is advertised in error message. Expected results: Maximum number for limit-usage will be lower so it can be applied or functionality will allow to set LONG.MAX - 1.
Patch submitted upstream: http://review.gluster.org/#/c/10022/
[root@darkknight ~]# gluster v quota vol0 limit-usage / 9223372036854775700 volume quota : success [root@darkknight ~]# gluster v quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 8192.0PB 80% 12.0KB 8192.0PB No No [root@darkknight ~]# gluster v quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 8192.0PB 80% 12.0KB 8192.0PB No No /test 819.2PB 80% 0Bytes 819.2PB No No Verified this bugs on glusterfs 3.7.0 built. marking this bugs as verified.
Hi Vijai, The doc text is updated. Please review the same and share your technical review comments. If it looks ok, then sign-off on the same. Regards, Bhavana
Doc-text looks good to me
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. https://rhn.redhat.com/errata/RHSA-2015-1495.html