Hi,
I have a running Virtualmin Pro system running since few years and never got issues with quota before that I use for all customers on it.
I have recently started to offer accounts with larger quota and I hit a strange issue. System doesn’t want to setup any quota above 3.7To. I have lot of space still on the partition involved.
Here is error when I try to setup a 4To quota for example:
Changing disk quota ..
.. Administration user failed : setquota: Cannot set quota for group 1018 from kernel on /dev/md4: Numerical result out of range setquota: Cannot write quota for 1018 on /dev/md4:
After doing some searches on internet, it looks like i need to “upgrade” quota but not sure I can do that safely regarding quotas of existing accounts.
@vincen This looks like the ext4 quota file format limit rather than any kind of Virtualmin quota-related issue.
It looks like the filesystem is using the older ext quota file format, vfsv0, which can hit a limit around the 4 TiB range when setting quota limits.
@Jamie, I think the fix should be to stop creating new ext quota files as vfsv0. In virtualmin-config, the ext4 setup currently uses plain quotacheck -vgum.
We should create quota files with -F vfsv1 where external quota files are used.
And, “Disk Quotas” module should also prefer vfsv1 over vfsv0 when creating or checking ext quota files.