Question Request to Implement Inode Limits for Shared Hosting Accounts

[Thomas Oryon]

Server operating system version

Rhel 9

Plesk version and microupdate number

18.0.78

Hello Support

We are currently using Plesk shared hosting on our server. We would like to implement inode limits for all hosting accounts to ensure stable performance. Specifically, we would like to:

1. Limit the total number of inodes (files and directories) per account to 75,000.
2. Limit the number of immediate child files in a directory to 2,500.

Currently, our cgroup setup limits CPU, RAM, and I/O, but we understand that inode limits cannot be enforced through cgroups. We would like to know:

• If Plesk natively supports inode quotas per subscription, or if Linux user quotas (setquota) is the recommended approach.
• The best method to enforce these limits automatically for all accounts.
• Any precautions or potential impacts we should be aware of when applying inode limits.

Could you please advise on how we can implement this on our server?

Thank you for your assistance.

 

[scsa20]

There's no native support for inode quotas. The recommended way would be to use linux user quotas with the setquota and limit it to the system user account of the subscription in question or set up a custom script to do the checks and enforcement.