Hide Forgot
Description of problem: setquota: Cannot set quota for user 509 from kernel on /dev/sdb1: Numerical result out of range setquota: Cannot write quota for 509 on /dev/sdb1: Numerical result out of range Version-Release number of selected component (if applicable): RHEL6 2.6.32-37.el6.x86_64 How reproducible: Always Steps to Reproduce: 1.mkfs.ext4 /dev/sdb1 2.mount -o usrquota /dev/sdb1 /mnt/mp1 3.quotacheck /mnt/mp1/ 4.quotaon /mnt/mp1 5.setquota -u quotausr $((2**32)) 0 0 0 /mnt/mp1 Actual results: Numerical result out of range Expected results: Set successly Additional info: [root@quota-dxk bangzi]# lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 6.0 Beta (Santiago) Release: 6.0 Codename: Santiago [root@quota-dxk bangzi]# uname -r 2.6.32-37.el6.x86_64
> Can not set the quota limit up to 4G Did you want to say _above_ 4G? > mkfs.ext4 /dev/sdb1 > mount -o usrquota /dev/sdb1 /mnt/mp1 > setquota -u quotausr $((2**32)) 0 0 0 /mnt/mp1 There are more formats how to store quotas into auxiliary file (aquota.user and similar) on the file system. The default format, called `vfsv0', supports 32bit values only. Thus this format has 4G limit. New 64b format, called `vfsv1', lifts up the limit to 16E. To use this newer format that must be journaled, you need to ask mount(8) explicitly: $ mount -o jqfmt=vfsv1,usrjquota=aquota.user /dev/sdb1 /mnt/mp1 The `jqfmt' option defines format, the `usrjquota' defines auxiliary journaled file where to store the limits on the files system. In addition, because of journaling, expensive quotacheck after crash does not need to be performed. To get vfsv1 quota format working, you need to have enabled support in Linux and in user space quota tools. Support in quota tools is planned for RHEL-6.1 update. Are you satisfied with this answer?
thanks a lot!
Verified according to https://beaker.engineering.redhat.com/jobs/62389.
Hi, I am reviewing and editing erratum: http://errata.devel.redhat.com/errata/stateview/10703 and would need some more details for this bug to state all the necessary points. Could you give a few key words to the points I pasted into the Technical Notes field. Once I have the text I can start on the approval process. Thanks
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause What actions or circumstances cause this bug to present. Consequence What happens when the bug presents. Fix What was done to fix the bug. Result What now happens when the actions or circumstances above occur. Note: this is not the same as the bug doesn’t present anymore.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,9 +1 @@ -Cause +See bug #609795. This is duplicate.- What actions or circumstances cause this bug to present. -Consequence - What happens when the bug presents. -Fix - What was done to fix the bug. -Result - What now happens when the actions or circumstances above occur. - Note: this is not the same as the bug doesn’t present anymore.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0716.html