Disk quotafield is greyed-out for a domain and it is not possible to edit it.
Subscription cannot be synchronized with the corresponding service plan due to not supported hard disk quota, the following message appears:
Syncing the subscription with its service plan failed because some of the services or resources defined in the plan cannot be actually provisioned with the subscription. Available value indicates the actual state of a resource or a service in the system. Clicking OK will initiate setting the subscription values according to the available values.
"Unlimited. Hard disk quota is not supported due to the configuration of the server file system."
Unconfigured disk quota in operating system.
Make sure that the quota is supported by the kernel. It should be compiled into the kernel or loaded as a module.
To check if the quota is configured properly use this command:
# /usr/local/psa/admin/sbin/usermng --isquotable
Normally, it should return "0."
If the utility returns the following error message
usermng: Unable to turn on user quota. User quota not supported on device '/dev/sda3' System error 3: No such process
Then make sure that the quota is enabled in
/etc/fstabfor the partitions Plesk stores data on. Add
usrquotaas in the example:
/dev/hda1 / ext3 defaults,usrquota 1 1
The partition must be remounted after
usrquotais added into
/etc/fstab, for example, with the following:
~# mount -o remount /
Create, check and repair quota files:
/sbin/quotacheck -cfmvF vfsv0 /
Note: If the command is unknown, install
Update the user quota with this command line:
~# quotaon /dev/hda1
Make sure that the
aquotaformat is used. There should be an
aquota.userfile in the root of every partition where the quota is enabled. If there is the
quota.userfile remove it and create correct one:
~# rm -f quota.user ~# touch aquota.user ~# /sbin/quotacheck -fmv /dev/hda1
Note. Use your own device instead of
Refresh Plesk components to update information about quota:
Home > Tools & Settings > Server Components > Refresh
Note that a separate component will not appear, but Plesk components cache will be updated to include new information.
If you are running Plesk in a Virtuozzo Container (CT)
Make sure that the
quotaugidlimitparameter is not set to zero and that it is greater than the number of users and groups in the CT. This limit can be adjusted from the Hardware Node with the following:
~# vzctl set CTID --quotaugidlimit 500 --save ~# vzctl stop CTID ~# vzctl start CTID
Where CTID is the ID of the Virtuozzo container with Plesk.
packagemngutility to recreate the backend cache in Plesk:
Please refer to this article if you need to configure quota on FreeBSD.