Resolved 550 Can't create directory: Disk quota exceeded

[adler96]

I have a site with a large number of files; about 30.000 files (nightearth.com).

I am trying to update a couple of files, and I am getting the error:

550 Can't create directory: Disk quota exceeded​

The DirectAdmin control panel says I have 50.005 inodes in use. Why would this be the case? I don't have that many files.

 

[adler96]

I can see there are 16.896 files under /.cagefs/opt/alt/php73/var/lib/php/session

Would it be safe to delete them?

 

[spacresx]

normally, its advised NOT to remove any files except the files listed in your
"domains/site-name/public_html/" folder.
If you edit/delete any other files/folders you risk killing your website and control panel.

I would wait for staff to reply to your original question. before taking action.
just saying.

https://x15.x10hosting.com:2222/user/filemanager?path=/domains

 

[garrettroyce]

This is a known bug in CageFS. You can delete these files. It should happen automatically after 30 days, but it looks like that didn't happen. I'm going to flag an admin to see if there's a reason this is happening to you.

https://docs.cloudlinux.com/cloudlinux_os_components/#tmp-directories

HOWEVER...

Backups are always the responsibility of the user. Before making any changes, make sure you have a backup.

Try to delete enough to bring your inode count down to 49,999. If you have a few files you know are junk, go ahead an clear them up. Click the checkbox next to the directory ~/.cagefs/ and then select the "compress" option from the top of the file list. This will make a .tar.gz file which is a backup of all individual 16k files. Download that file. You can then delete the entire folder (make sure you delete it from the trash as well). This should free some inodes.

x10hosting free users cannot have more than 50,000 inodes. An inode is a file, folder, link, and very rarely special "files" that should not be present on your account. If you're really interested, you can check out linux character devices and hardlinks. I highly doubt your account would have either, but they would count to that limit and they can be deleted just like files anyway.

 

[adler96]

Thanks for your answer; I won't delete the files for now; I'll leave them in case admins need them to analyse what's going on.

These 16000 files seem to be from the last 4 or 5 days, and lots of them even from the same minute (though it's hard to tell through the web interface).

 

[Anna]

Session files are generally safe to delete, they may cause someone to have to re-login and to re-apply some settings and other things like that, but would not break the site in themselves.

However, that many session files in a short time can indicate two things.

One being the site has become to popular to be suitable on the free hosting environment. Our premium hosting allows for 300 000 inodes in the regular tier, with possible to upgrade to plus plans.

The other thing might be that there's something in the code that causes a spawn of session files under a certain situation. A majority of the files were created the same date, and roughly during a 30 minute period from what I can tell. This may be a clue in itself, did you do something in particular around that time?

Given that they were all created at the same time, they would not clear until around 7th of July by the automated system (30 days after they were created), so I doubt that it is caused by not being cleared properly by cageFS, at least not with the information at hand.