Inodes Increase Since Upgrading To 4.7.1 (From 4.6.3)

Hi,

We upgraded from 4.6.3 to 4.7.1 on January 29th and since then our INODES usage has exploded and we are having to clear the cache every 2 weeks or earlier.

Seems the new version is caching a lot more files than before and our limit is 250,000 files.

What can be done about this without going to the next level of hosting plan which is double in price.... Inodes is the only issue as space is ok and we are hardly using any of the hosting resources.

On 4.6.3 we were constantly at approx 130,000 inodes for months without clearing cache.

Since upgrading to 4.7.1 the indoes jumps from 77,000 after clearing cache to over 200,000 within 10 days or so.

Hi,

We upgraded from 4.6.3 to 4.7.1 on January 29th and since then our INODES usage has exploded and we are having to clear the cache every 2 weeks or earlier.

Seems the new version is caching a lot more files than before and our limit is 250,000 files.

What can be done about this without going to the next level of hosting plan which is double in price.... Inodes is the only issue as space is ok and we are hardly using any of the hosting resources.

On 4.6.3 we were constantly at approx 130,000 inodes for months without clearing cache.

Since upgrading to 4.7.1 the indoes jumps from 77,000 after clearing cache to over 200,000 within 10 days or so.

Then go with a dedicated server and increase your disk space.

A symptom solution is to use something like our EZ Admin Helper that allows you to clear your cache at a frequency you select.

There's nothing in the release itself that increases inode counts that dramatically. I'd suggest you review your var/backups directory for any really old upgrade backups that might be there as well as your var/files/exim/backup/images directory which cs-cart uses when importing/exporting images/ After import/export they are no longer used and cs-cart is not great at cleaning up after themselves.

If you have SSH access, you can use 'find' to determine file usage by directory. I.e.

# cd /home/you/public_html

# find . -type f | wc

You can follow the usage and find the directories that are holding the most files and determine if they're necessary. Most likely your increase is in the var directory but is NOT related to the cache.

Thank you tbirnseth for the detailed answer and helpful hints.

Inodes usage up to 4.6.x has never been an issue, since 4.7 update its gone up heaps.... possibly more caching but ill investigate soon.