There are 32 cores in a system (2 cpus each 16 cores) and I want to limit a user to use only 4 cores (100% usage for that 4 cores). There are two kernel parameter for that according to the manuals: cpu.cfs_quota_us and cpu.cfs_period_us An example on the kernel.org document says: With 500ms period and 1000ms quota, the group can get 2 CPUs worth of runtime every 500ms. # echo 1000000 > cpu.cfs_quota_us /* quota = 1000ms */ # echo 500000 > cpu.cfs_period_us /* period = 500ms */ I want to know how those ms are determined? In my case, I think the quota is 32000000 and the period is 4000000. Am I right? The content of etc/cgconfig.conf is: group ansys { cpu { cpu.cfs_quota_us = 32000000; cpu.cfs_period_us = 4000000; } memory { memory.limit_in_bytes = 8000m; } } But it doesn't work! and I get an error when I run /etc.init.d.cgconfig start, I get this error: Failed to parse /etc/cgconfig.conf or /etc/cgconfig.d [FAILED]Starting cgconfig service: /sbin/cgconfigparser; error loading /etc/cgconfig.conf: Failed to remove a non-empty group

On two of my VMs the crontab -e command fails to create a directory in /tmp but it works with mkdir:

/tmp/crontab.oxyaBy: Input/output error
Creation of temporary crontab file failed - aborting

strace output:

root@vm:~# strace crontab -e
mkdir("/tmp/crontab.1SuJe9", 0700)      = -1 EIO (Input/output error)

root@vm:~# strace mkdir /tmp/crontab.1SuJe9 -m 700
mkdir("/tmp/crontab.1SuJe9", 0700)      = 0

Both VMs are running Ubuntu 16.04.6 LTS (4.4.0-173-generic x86_64) This is reproducible every time and the problem persists after reboots, fsck says everything is fine and there are no other issues on this VMs. I already tried to reinstall the cron package but nothing changed. Any ideas? Thank you! **Edit:** dmesg shows

EXT4-fs (dm-0): Quota write (off=4080, len=40) cancelled because not block aligned
Quota error (device dm-0): v1_commit_dqblk: dquota write failed

The crontab command works with quotaoff but I still would love to know why crontab and mkdir behave differently...

I'm using Debian Linux. I want to determine user base page limit, different page limit for different users, for a printer. I can determine page limit for printer with CUPS but can not determine page limit for single user. How can I achieve this?

I have exceeded my disk quota on a system which I do not have root access. I tried removing old files but am still over. I tried runing du to find where I am using up all my space but it reports I am using very little. Results from quota /home/1234$ quota -s Disk quotas for user 1234 (uid 1234): Filesystem space quota limit grace files quota limit grace cslab:/home 4519M* 4096M 5120M 09:47 6155 0 0 From du /home/1234$ du -mad 1 ... 936 total I don't understand why quota says I am using 4.5GB while du only counts .9GB. I also checked for files I own in /tmp and there was 50MB worth of files there. *Where could the other 3.5GB of files be? Is it possible the quota system is wrong and needs reset?*

I am using Pop! OS on a workstation PC in my workplace. However, today the machine crashed into a recovery mode on boot, apparently because the /Home filesystem wouldn't mount. The filesystem is ext4 and is in a partition on an NVME SSD. When I try to mount the partition manually as root, I get the following error: mount: /home: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, or other error. dmesg shows the following lines that seem to be relevant: [ 193.536359] EXT4-fs warning (device nvme0n1p4): ext4_enable_quotas:7092: Failed to enable quota tracking (type=0, err=-22, ino=3). Please run e2fsck to fix. [ 193.536593] EXT4-fs (nvme0n1p4): mount failed [ 316.932127] kauditd_printk_skb: 17 callbacks suppressed [ 316.932131] audit: type=1400 audit(1717275233.956:29): apparmor="DENIED" operation="file_inherit" class="file" profile="man_groff" name="/dev/tty1" pid=1149 comm="preconv" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 316.935702] audit: type=1400 audit(1717275233.960:30): apparmor="DENIED" operation="file_inherit" class="file" profile="man_groff" name="/dev/tty1" pid=1150 comm="tbl" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 316.939852] audit: type=1400 audit(1717275233.964:31): apparmor="DENIED" operation="file_inherit" class="file" profile="man_groff" name="/dev/tty1" pid=1158 comm="troff" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 354.323345] EXT4-fs warning (device nvme0n1p4): ext4_enable_quotas:7092: Failed to enable quota tracking (type=0, err=-22, ino=3). Please run e2fsck to fix. [ 354.323699] EXT4-fs (nvme0n1p4): mount failed [ 650.591473] EXT4-fs warning (device nvme0n1p4): ext4_enable_quotas:7092: Failed to enable quota tracking (type=0, err=-22, ino=3). Please run e2fsck to fix. [ 650.591697] EXT4-fs (nvme0n1p4): mount failed I tried running e2fsck, as the messages suggest. It didn't report any errors - just said the journal was recovered and reported numbers of nodes and files. However, the partition still wouldn't mount afterwards. There are other partitions on the drive that did seem to mount fine. It seems strange, because everything was working until I shut the machine down for maintenance. But then, when I tried to power back on, this error occurred. Does this likely mean the SSD is failing and should be replaced? Are there any (simple) options for recovering the filesystem/data? **Update:** Per the dmesg log, the issue seems to relate to user quotas. I have user quotas enabled on the /home partition, but I'm not sure where this mounting error is suddenly coming from. Does anyone have any ideas of what I can try?

Using RHEL 8.9, I have xfs_quota applied to each home account folder under /home. In doing xfs_quota -x -c 'limit bhard=1g ron' /home I can observe for example a cp fail when trying to copy a single file greater than the *bhard limit* of 1 gb into /home/ron/. That makes sense to me. However if I only set limit bsoft=500m, and do not do a hard limit, **what actually happens?** Because with a soft limit I can exceed that and there is no indication to me (if I am acting like a typical naive user) so it somewhat seems pointless? Someone tell me how as an admin I would use bsoft either by itself or in conjunction with a bhard limit to manage users carelessly dumping and leaving too much data in their home account. Is there any reason to not do just a limit bhard=1gb on people's home account and let them find out the *bhard* way ?

in RHEL 8.9, I have a 100gb XFS formatted /home partition; all local user accounts in /etc/passwd have their home directories under /home. And all user accounts primary gid is and will always be 100 {users}. I would like to apply a quota of 1GB per user on their /home account as an administration effort to manage data. I have 80 users currently in /etc/passwd can expect it to grow back up over 150. I currently have in /etc/fstab UUID=12345 /home xfs defaults,nodev,nosuid,uquota,gquota 0 0 - What are the correct arguments to pass to the xfs_quota command? - If I have 80 users, do I have to do 80 xfs_quota commands one for each account under /home? Or can it be done with one command instance? - should a mount -o remount /home work? I'm finding it doesn't and either a successful umount or reboot is needed. Will a umount -l work? How dangerous is this on an active system with users logged in? - For all new users in the future, will a new xfs_quota need to be performed on their home folder or is there a way to have it automatically applied?

I'm trying to set up default disk quotas for every new user that gets an account created in my Debian10 server. For example, user1 gets an account created and the first time he logs in the system (through ssh or su or whatever) his account gets a 100MB disk quota hard limit without the manual intervention of the server admin. I've made a perl script that lets me set disk quotas for a user but it only works when used by root, which makes sense since a user could modify his own quotas. But is there a way to use it with a pam module maybe so that a user quotas are set up automatically? Is there another (maybe better) way to set these automatic disk quotas for all the incoming new users?

I have a fresh Debian 12 system and I'm trying to turn on and enforce EXT4 filesystem quota. I read a lot of man and some other sources, for example this one from Red Hat: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_file_systems/limiting-storage-space-usage-on-ext4-with-quotas_managing-file-systems And I cannot make it work and after several hours of trying I'm confused. I do not know, if there is a sane way to do this or am I missing something. Let's try it on a loop file.

vagrant@bookworm:~$ sudo dd status=progress if=/dev/zero of=ext4_fs bs=1M count=1000
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB, 1000 MiB) copied, 0.595179 s, 1.8 GB/s

vagrant@bookworm:~$ sudo mkfs.ext4 ext4_fs 
mke2fs 1.47.0 (5-Feb-2023)
Discarding device blocks: done                            
Creating filesystem with 256000 4k blocks and 64000 inodes
Filesystem UUID: 2d5eedba-eada-4b9f-ba88-e182b3ff24fa
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376
Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

vagrant@bookworm:~$ sudo tune2fs -O quota ext4_fs 
tune2fs 1.47.0 (5-Feb-2023)

vagrant@bookworm:~$ mkdir mountpoint
vagrant@bookworm:~$ sudo mount ext4_fs mountpoint/
vagrant@bookworm:~$ ls mountpoint/
lost+found

vagrant@bookworm:~$ sudo quotaon -v -p mountpoint/
group quota on /home/vagrant/mountpoint (/dev/loop0) is on (accounting)
user quota on /home/vagrant/mountpoint (/dev/loop0) is on (accounting)
project quota on /home/vagrant/mountpoint (/dev/loop0) is off

So far so good. Now, are files aquota.user or aquota.group required? If so, they should be created automatically using the quotacheck command:

vagrant@bookworm:~$ sudo quotacheck -cugm mountpoint/
quotacheck: Cannot find filesystem to check or filesystem not mounted with quota option.

Weird. When I remount the system ro, the command starts, but obviously cannot work properly and write those files:

vagrant@bookworm:~$ sudo quotacheck -cugm mountpoint/
quotacheck: Cannot create new quotafile /home/vagrant/mountpoint/aquota.user.new: Read-only file system
quotacheck: Cannot initialize IO on new quotafile: Read-only file system

When I try to enforcing the quota, I add usrquota to fstab and reboot.

/home/vagrant/ext4_fs /home/vagrant/mountpoint ext4 rw,nodev,nosuid,defaults,usrquota 0 0

Quotas are enforced, but aquota.user file is missing, I still cannot run quotacheck, and now systemd is added to the mix, with failed quotaon.service:

vagrant@bookworm:~$ sudo systemctl status quotaon.service 
× quotaon.service - Enable File System Quotas
     Loaded: loaded (/lib/systemd/system/quotaon.service; static)
     Active: failed (Result: exit-code) since Sun 2023-09-24 15:18:07 UTC; 8min ago
       Docs: man:quotaon(8)
    Process: 359 ExecStart=/sbin/quotaon -aug (code=exited, status=1/FAILURE)
   Main PID: 359 (code=exited, status=1/FAILURE)
        CPU: 1ms

Sep 24 15:18:07 bookworm systemd: Starting quotaon.service - Enable File System Quotas...
Sep 24 15:18:07 bookworm quotaon: quotaon: using . on /dev/loop0 [/home/vagrant/mountpoint]: File exists
Sep 24 15:18:07 bookworm systemd: quotaon.service: Main process exited, code=exited, status=1/FAILURE
Sep 24 15:18:07 bookworm systemd: quotaon.service: Failed with result 'exit-code'.
Sep 24 15:18:07 bookworm systemd: Failed to start quotaon.service - Enable File System Quotas.

And there is also:

vagrant@bookworm:~$ sudo systemctl status systemd-quotacheck.service
● systemd-quotacheck.service - File System Quota Check
     Loaded: loaded (/lib/systemd/system/systemd-quotacheck.service; static)
     Active: active (exited) since Sun 2023-09-24 15:18:07 UTC; 12min ago
       Docs: man:systemd-quotacheck.service(8)
    Process: 354 ExecStart=/lib/systemd/systemd-quotacheck (code=exited, status=0/SUCCESS)
   Main PID: 354 (code=exited, status=0/SUCCESS)
        CPU: 3ms

Sep 24 15:18:07 bookworm systemd: Starting systemd-quotacheck.service - File System Quota Check...
Sep 24 15:18:07 bookworm systemd: Finished systemd-quotacheck.service - File System Quota Check.

What is the sane way in 2023 to configure disk quotas? Kind regards.

Maybe there is a better way to do what I am trying to achieve, so let me describe the whole problem. My / and /home directories are on a separate LV. It happened so the / LV get out of space. I then backup my /home and try to remove it to be able to resize /. However, when I did login to root tty and try to umount the /home with lvchange -a n /dev/trixxxy-vg/home I get prompt that this logical volume is in use. Logical volume trixxxy-vg/home contains a filesystem in use. My .emacs.d and .bashrc directories in /root were links to /home/user/ relevant, so I thought that can cause the problem, but after removing them nothing have changed. I guess there is a way, that I am not aware of, to check what file is currently using the particular logical volume. Or may one force remove such partition?

I want to add quota per user in my Apache2 webroot. My /var/www directory is not a partition. I've found tutorials on how to set up quota for partitions, but how do I set up /etc/fstab without moving the directory to another partition? By the way: How many MB is a Block in block-hardlimit?

Google has parsed [this Duke University IT knowledgebase article](https://www.cs.duke.edu/csl/faqs/quotas_about) into an infocard alleging to _anyone_ searching "linux quota block size" that > A block quota is the limit on the actual amount of disk space that can be used by an account. This space is measured in 1 KB blocks (1 KB = 1024 bytes or characters). A quick search on this site yielded [this answer](https://unix.stackexchange.com/a/232219/26420) referring to *other* definitions of "block size", including EXT4's: > A typical block size is 4KiB. I poked around in [these source files](https://kernel.googlesource.com/pub/scm/utils/quota/quota-tools/+/refs/tags/v4.04) a bit, but their code is so sparsely commented that I was unable to grok it. I still vaguely **assume** that quota(1) reports "block size" in the associated filesystem's specific block (size rather than a universal constant like 1KiB), but how could I **verify** this? Where is the point of contact between the quota tooling codebase and the filesystem driver codebase?

I've been bumping up against this issue for years, but have never been able to find a resolution. Prior to RHEL7 (i.e. RHEL 5, RHEL 6, and CentOS 6), I was able to... 1. Implement user quotas on my NFS servers, via the usrquota option in the /etc/fstab file 2. Mount the NFS shares to a cluster of various EL clients (RHEL 5 & 6, CentOS 6, Fedora 17 thru 21, Pidora, and even Raspbian) 3. Enforce quotas across **all** of those clients 4. Query quotas via the quota command on **ALL** of those clients ***Problem:*** With CentOS7, I have made the jump to XFS (from ext4), and I am able to do all of the above **except** "*4. Query quotas via the quota command on **ALL** of those clients*", and the xfs_quota command **also does not** report any information relating to the XFS formatted file systems mounted from the NFS Server with quotas enabled. The CentOS7 NFS Server **does** enforce those quotas, which is useful to my administration of the NFS Server, but frustrating for hundreds of NFS Client users as well as when supporting users who repeatedly run into quota limitations. The following "Workaround" allows users to query disk usage of their NFS mounted file systems, but is **not** an accurate or sufficient substitution for quota/xfs_quota queries, nor is it an intuitive solution for most users... du ‐s .[A‐z]* * | sort ‐n I've danced around this issue long enough, and would really appreciate if this community could assist with my understanding why reporting user quotas across my XFS formatted NFS shares is not working. RHEL support, and CentOS support forums are all turning up empty. Assistance would be appreciated! ***Notes:*** - I have the uquota,gquota options in the /etc/fstab file on the NFS Server, as so... /dev/mapper/nfs-home /home xfs defaults,uquota,gquota 0 0 - The following is the NFS mount entry in the NFS Client /etc/fstab file... 123.45.67.89:/ /home nfs rw,hard,intr,bg 0 0 - The rpcbind, quotad and rquotad TCP & UDP ports are opened in the Server's firewall. - There are subnet entries for the rpcbind, quotad, and rquotad services in the /etc/hosts.allow file. - A df query on the NFS Client(s) shows the mounted NFS shares, while the xfs_quota -c 'df' command does **not** return any NFS mounted file systems. ***I am happy to provide more information on the Client-Server relationship if anyone shows interest.***

I mount /tmp on tmpfs using: sudo systemctl enable tmp.mount sudo systemctl start tmp.mount But this way /tmp takes up all the free RAM: $ df -h /tmp Filesystem Size Used Avail Use% Mounted on tmpfs 3.9G 12K 3.9G 1% /tmp $ **How do I tell systemd tmp.mount to use only 1G?** I know I can alternatively not use systemd and manually add an entry to /etc/fstab and specify the size there. But I don't want to do that. I want to use systemd backed tmpfs.

I am getting 'disk quota exceeded' error but the partition is not full and user has unlimited quota. What is wrong and how can I fix it? xxx@mc:/tmp$ pyenv install 3.7.6 /home/xxx/.pyenv/plugins/python-build/bin/python-build: line 2048: cannot create temp file for here-document: Disk quota exceeded mkdir: cannot create directory ‘/tmp/python-build.20220629235336.143991’: Disk quota exceeded BUILD FAILED (Ubuntu 20.04 using python-build 20180424) Inspect or clean up the working tree at /tmp/python-build.20220629235336.143991 xxx@mc:/tmp$ df -h Filesystem Size Used Avail Use% Mounted on udev 445M 0 445M 0% /dev tmpfs 98M 1016K 97M 2% /run /dev/sda 19G 11G 7.5G 58% / tmpfs 489M 0 489M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 489M 0 489M 0% /sys/fs/cgroup /dev/sdc 4.8G 20M 4.7G 1% /baks tmpfs 98M 0 98M 0% /run/user/0 xxx@mc:/tmp$ quota -u Disk quotas for user xxx (uid 1000): none

I'm trying to enable journaled usrquota on Debian 11 Kernel 5.10. All information I find uses external files which leads to the following deprecation warning:

quotaon: Your kernel probably supports ext4 quota feature but you are using external quota files. Please switch your filesystem to use ext4 quota feature as external quota files on ext4 are deprecated.

My fstab entry uses the options errors=remount-ro,usrjquota=aquota.user,jqfmt=vfsv1 Which as far as I understand should enable ext4 qouta feature. However after a reboot when I run sudo quotaon -v / I get a deprecation warning and complains about missing aquota.user file. What confuses me is: Why do I have to specify a file name for usrjquota... As far as I understand the point of journaled quota is that we don't need a file any more. If someone could provide the steps to enable journaled ext4 quotas it would be really appreciated.

I have already configured my server to work with user quotas and everything works well. I can modify user quota with the edquota command. How can I do this programmatically, from a bash script for example?

I am unpacking a tar file when I have error messages like this: [xxxxx@lo-login-02 ~]$ tar -xvf ontonotes-release-5.0_LDC2013T19.tgz ...... (omitted lines) tar: ontonotes-release-5.0/tools/ontonotes-db-tool-v0.999b/src/on/__init__.py: Cannot open: No such file or directory ontonotes-release-5.0/tools/ontonotes-db-tool-v0.999b/LICENSE tar: ontonotes-release-5.0/tools: Cannot mkdir: Disk quota exceeded tar: ontonotes-release-5.0/tools/ontonotes-db-tool-v0.999b/LICENSE: Cannot open: No such file or directory ontonotes-release-5.0/tools/ontonotes-db-tool-v0.999b/INSTALL tar: ontonotes-release-5.0/tools: Cannot mkdir: Disk quota exceeded tar: ontonotes-release-5.0/tools/ontonotes-db-tool-v0.999b/INSTALL: Cannot open: No such file or directory ontonotes-release-5.0/tools/ontonotes-db-tool-v0.999b/setup.py tar: ontonotes-release-5.0/tools: Cannot mkdir: Disk quota exceeded tar: ontonotes-release-5.0/tools/ontonotes-db-tool-v0.999b/setup.py: Cannot open: No such file or directory ontonotes-release-5.0/index.html tar: ontonotes-release-5.0/index.html: Cannot open: Disk quota exceeded tar: Exiting with failure status due to previous errors I have checked my file system quota, Inodes and disk space, but they all seem to be fine: [xxxxx@lo-login-02 ~]$ quota Disk quotas for user xxxxx (uid 198587): Filesystem blocks quota limit grace files quota limit grace lo-ne-home3:/home3 9005516 16777216 20971520 100000* 80000 100000 [xxxxx@lo-login-02 ~]$ df -i Filesystem Inodes IUsed IFree IUse% Mounted on lo-ne-home3:/home3/xxxxx 21251126 122640 21128486 1% /cluster/home/xxxxx [xxxxx@lo-login-02 ~]$ df -h Filesystem Size Used Avail Use% Mounted on lo-ne-home3:/home3/xxxxx 1.0T 8.5G 1016G 1% /cluster/home/xxxxx

In our company, we use a headless Linux machine as development machine. However, sometimes users use up all resources (CPU, RAM) on that machine, which influences the work of others. Hence, we want to cap the amount of resources a user can take up for a single process. Is there a utility on Linux that allows to limit the total amount of resources a user can use? Or that automatically kills processes that use up too many resources?

[INFO] Adding quota to fstab. [ERROR] Exception occured: ISPConfigOSException -> Command mount -o remount / 2>&1 && quotaoff -avug 2>&1 && quotacheck -avugm 2>&1 && quotaon -avug 2>&1 failed. (/ispconfig.ai.php:15) what should I do?