When storage where cache stores files it will stop writing new cache items.

www-data@4c24e21b55f5:~/html$ drush cs test "test"
www-data@4c24e21b55f5:~/html$ drush cg test
The test2 object in the test bin was not found.                                          

It is quite stupid behavior because when cache grows too much it will practically stops caching new things. And this could happen more often if it is stored in /dev/shm.

In case of write error because off full storage it should instead try to clean oldest or long time not accessed files. Or at least clear whole cache.

Comments

Bobík created an issue. See original summary.

Collins405’s picture

This is critical for us now.

Warning: fopen(/homepages/28/d632746599/htdocs/vehiclesave.co.uk/sites/default/files/.ht.filecache/cache_bootstrap-variables): failed to open stream: Disk quota exceeded in DrupalFileCache->set() (line 238 of /homepages/28/d632746599/htdocs/vehiclesave.co.uk/sites/all/modules/dev/filecache/filecache.inc).

This message shows publicly, even with error messages turned off!

I am disabling this module until we can find a work around.

Collins405’s picture

Priority: Normal » Critical
Collins405’s picture

On our site, a file count in the .ht.filecache directory is coming out at 460,000+ files, its maxing our file count quota, but not our space quota.

Is anyone else experiencing this? Cron runs regularly, but cant cope with the number of generated files.

ogi’s picture

Xoruna’s picture

I'm having the same issue, is there any chance to see progress about this?

BTW, this module remains very helpful anyway, thanks!

Edit: a possible workaround is to create a cron job that clears all caches in a frequency depending on how much trafic there is on the concerned website. It is doable by installing the CacheFlush module and the Elysia Cron module, or with the Ultimate Cron module which needs a bit of development to import a cron rule.
However, a real solution with Filecache remains better.