Can I be banned for reaching the inode limit?

Hosting Support
1

I have a server on fervian.rf.gd with a WordPress installation and it’s subdomain social.fervian.rf.gd with a HumHub installation.
After installing HumHub the inode counter increased exponentially to the point where I have a small social network for my friends using ~48k inodes.
I will remove the WordPress installation but I don’t think that this will solve my problem…
Can someone tell me if I can be banned for using that much inodes or how can I reduce the usage

2

No

Just delete files and directories that you do not need

9 Likes
3

Thanks!

2 Likes
4

I’ve ran out of inodes before and you don’t get banned, but many things on your site stop working, because they can’t create files.

3 Likes
5

Hi Adrrrrien,

You won’t be banned for using high inodes, and yes inode is quite a headache for most web developers, be it free hosting or paid hosting, this is the same.

As you have mentioned about having a social platform application, it must have involved caching images like previews, thumbnails or even profile pictures. Consider removing the cache copies and limiting the sizing versions of your application. This way you can avoid having different copies of the same content on your account. Meanwhile, you can remove profile pictures completely if that’s not vital or you can choose to use a profile picture service like Gravatar and pull images from them instead.

You may also want to move small text file content to the database if you could. This way you’re also saving on creating more small files that aren’t necessary most of the time. Periodically clearing the applications log folder (download then delete on the server) is also a good way to reduce inode usage.

However, as the TOS has also mentioned moving everything to the database as inode-limit evasion can cause suspension, so you need to selectively and reasonably do that if you have to save inodes. They won’t ban you because you did it in a reasonable approach.

By reasonably, converting a previously stored-as-text list of user-shared URLs as database rows is definitely acceptable. While keeping a 1GB video chopped into multi-megabyte blobs is not. I guess this is more of a common-sense-determined approach.

If your application creates other types of files that are for your reference and does not affect functionality, consider downloading and removing those as well.

Cheers!

3 Likes