full harddisk due to wrong path in garbage collection

  • a multisite wordpress-blog with three blogs (/blog, /blog/new, /blog/newest) crashes due to full harddisk.

    many many files with rss-feed-content were written to $cache_path, but gc never deleted them. gc looks for files to delete in $blog_cache_dir, but there is nothing to delete (cache/blogs/blog) or path does not even exist (cache/blogs/blog/new, cache/blogs/blog/newest).

    two questions i have:
    – what exactly is written to $cache_path? rss-feeds are usually cached in $cache_path.’supercache’! why and what is stored in /cache?
    – why is gc looking for files to delete in paths that don’t even exist, but not in $cache_path, where millions of files wait to be deleted?

Viewing 3 replies - 1 through 3 (of 3 total)

  • The rss files should go in sub directories belonging to the blogs they were found.

    Are any other files being generated in the cache directory?

    Thread Starter michael.bliem

    (@mbportatour)

    they should, but they dont…

    there is a folder cache/blogs/blog with index.html and meta/index.html in it, nothing else. there are no folders like cache/blogs/blog/new or cache/blogs/blog/newest at all.

    only other file written to /cache is debug.log from wp_super_cache…

    Thread Starter michael.bliem

    (@mbportatour)

    it seems there was an update that changed something in the behaviour of the plugin. thanks for that!

    unfortunately, the plugin still creates massive amount of tmp-files in wp-content/cache/ directly…

    i tried to turn off ‘deliver supercache-file and create new one afterwards’.
    it doesn’t seem to work for feeds. nothing changes: every feed-request leads to creation of a new tmp-file. most of them are completely identical (checked with diff).

    what can i do?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘full harddisk due to wrong path in garbage collection’ is closed to new replies.