Thanks for the reply. I did spend some time searching and trying things before asking here.
Your suggestion “sudo modprobe quota_v2” didn’t appear to help.
I might have to try replicating my production server using the Vmin installer 7.0.2, as it appears there have been some issues with the recent versions.
I think this might be the key but I am not sure what it is pointing to.
“mount: (hint) your fstab has been modified, but systemd still uses
the old version; use ‘systemctl daemon-reload’ to reload.”
I installed minimal 9.2 and ran the installer -x (no updates) and it worked fine. I then updated it and still worked fine.
So, with 9.3 without any OS updates, the quota, usrquota and grpquota are added to fstab, but it still fails to activate quotas. Running “mount |grep quota” shows noquota.
Also, starting with 9.2 and updating the OS before installing Vmin still stops quotas
I tried clean install with RHEL 9.3 and it seems at first glance to work just as it always did with XFS, i.e. requiring to reboot the system to enable quotas:
I have taken a deeper look into it and it isn’t clear why xfs_quota -x -c 'report' returns nothing even though quotas are clearly enabled in /etc/fstab and /etc/default/grub. Also running xfs_quota -x -c 'limit bsoft=500m bhard=550m user1' / returns:
xfs_quota: cannot set limits: Function not implemented
It is confusing because XFS module is (always) loaded, e.g.:
Did you reboot after? AFAIK, XFS requires the filesystem be unmounted and remounted to enable quotas, which can only easily happen on a reboot if the filesystem is in use. The -o remount option or whatever doesn’t work for enabling quotas on XFS, I don’t think.
Sadly, I see the same issue in AlmaLinux 9.3 as well! It isn’t clear why quotas are not getting enabled even after reboot.
The main difference between clean Alma 9.3 install (where quotas don’t work), and previous installs (where quotas work) is that LVM is being used by default in the latest 9.3.
No, quotas with XFS in LVM simply don’t work. I don’t know what’s wrong! Presumably this is an upstream bug, maybe?
Yes, I’d be happy too to update Webmin to do the right thing. Sadly, there is nothing I could find neither in release notes nor in documentation about any changes and why it may not work. I’m afraid to spend that much time with it, as suspect it could happen to be the bug in upstream libraries.