Reduce inodes count on Magento website -

i getting errors on website , website inodes count overload. hosting inodes limit 200,000 website inodes count 909,496 , can't open phpmyadmin. hosting support asked me remove unused files. how can decrease inodes count , files unused in magento based website?

usually indicator need more capable hosting provider.

the major places magento creates files during operation in var/ folder , product image cache.

if you've never checked before, following areas can accumulate phenomenal amount of detritus. using ftp client, check following areas in var/ folder:

1. check don't have bazillion sessions files in var/session, remove older current date

2. check there aren't excessive amount of files in var/report, might want find out why magento generating them , fix issue. delete them all.

3. logging generate on time several huge files in var/log, delete them , @ new ones find out errors being generated.

4. imports , other stuff can cause temporary files accumulate in var/tmp, delete them. check in var/import old imports can deleted

stored database backups kept in var/backup, using admin backend system > tools > backups:

4. download latest database backups local workstation , delete backups.

magento uses lot of caching store information, biggest image cache if have large catalog, , contain cached images beginning of time, , lots of useless ones if you've deleted product on time. using admin backend, go system > cache management:

5. clear magento cache.

6. flush catalog images cache.

magento not delete product images when delete product. in fact magento prime candidate appearing on 1 of hoarder programs prevalent on tv there while.

7. after site working, consider installing imageclean.

hopefully have reduced inode count enough carry out following operations. before proceeding, couple database backups , store off server!!!

next step ask hosting provider if include database in inode table count. if do, kind of stuck magento uses innodb , likely, they've cheaply not set mysql use files-per-table can resize innodb file size optimizing each table. ask them if use files-per-table when set mysql, if don't know is, develop sinking feeling in pit of stomach.

some tables excessively huge, if you've haven't set set magento master cron job trigger in cpanel , checked make sure log table cleaning enabled in system > configuration > advanced > system > log cleaning. these tables follows:

        'dataflow_batch_export',         'dataflow_batch_import',         'log_customer',         'log_quote',         'log_summary',         'log_summary_type',         'log_url',         'log_url_info',         'log_visitor',         'log_visitor_info',         'log_visitor_online',         'index_event',         'report_event',         'report_viewed_product_index',         'report_compared_product_index',         'catalog_compare_item',         'catalogindex_aggregation',         'catalogindex_aggregation_tag',         'catalogindex_aggregation_to_tag' 

magento has built-in script clean logs. if running crashes memory error because you've never set cron job , there's bloat clean out, crucial web host has script can run manually delete log file contents. including dataflow tables won't cleaned out magento log cleaning process. if use dataflow import/export lot, nexcess has script can check on dataflow tables size , clear them well.

after cleaning database, need use phpmyadmin optimize each table in magento database. if hosting provider hasn't set files-per-table in mysql, squat reducing inode count.

after that, don't bother messing deleting application files or else magento uses. doesn't accumulate aside var/ folders , image cache , end dead website.

at point, you're @ mercy of shared server hosting plan has decided fair limiting can done in each account , doesn't allow enough resources run magento. start looking hosting provider supports magento, don't bother limiting inode count (a cheap trick allow many people share hard drive) offer plenty of disk space run e-commerce website.