Ages ago I installed the server using the automated 20.0.4 setup provided in the tutorials here and all has been OK, but just recently I have noticed that quotas are failing on boot, I'm perplexed as to what has stopped them working suddenly after all this time. Here is the relevant lines from my fstab, which obviously the automated install added :- [QUOTE# <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda2 during curtin installation /dev/disk/by-uuid/6a186569-59b1-4565-a04b-afe6c5ef2305 / ext4 defaults,usrjquota=quota.user,grpjquota=quota.group,jqfmt=vfsv0 0 0 # /boot/efi was on /dev/sda1 during curtin installation #/dev/disk/by-uuid/92C3-D158 /boot/efi vfat defaults 0 0 /swap.img none swap sw 0 0 ][/QUOTE] Happy to hear any clues that you may have.
Are you getting an error that indicates this? There are a few reasons why they would fail, starting with the error might help. What do you see running 'quotacheck -avugm; quotaon -avug'?
quotacheck: Quota for users is enabled on mountpoint / so quotacheck might damage the file. Please turn quotas off or use -f to force checking. quotaon: using //quota.group on /dev/sda2 [/]: Device or resource busy quotaon: using //quota.user on /dev/sda2 [/]: Device or resource busy
Does 'repquota -a' show quota info? It sounds like quotas are enabled, why do you think they are not?
Seems as though it is giving me quota details. *** Report for user quotas on device /dev/sda2 Block grace time: 7days; Inode grace time: 7days The only reason I raised the question is that on boot everything is showing green as it goes through the boot sequence with the exception of quota check which was showing as fail, however a reboot just now to check the exact warning has shown everything in the green, so it remains a mystery as to why I was getting a fail. Thanks anyway for your assistance, if it rears it's head again, I'll post the exact error in this thread.
