This error comes up occasionally when hitting non-cached URIs.
There is actually plenty of space available so the error is misleading - but I believe it is due to using up available inodes.
For now I'm just cleaning it up by sshing into the server and emptying the cache:
cd forum_archive/current
bin/rails tmp:cache:clear
But it's worth keeping an eye on to see how often it comes up.
Due to the manner of caching we are doing it's not feasible to expire cached URIs based on last access.
Additionally, many of these cached URIs are nonsense links that don't even resolve to anything other than a 404 in the archive (e.g., http://forum.biohack.me/index.php?p=/entry/register&Target=discussion%2F406%2Fwhat-do-you-feel-most-with-your-magnet-your-top-5%3F, which is a vanilla entrypoint that the rails redirect was never coded to handle).
This error comes up occasionally when hitting non-cached URIs.
There is actually plenty of space available so the error is misleading - but I believe it is due to using up available inodes.
For now I'm just cleaning it up by sshing into the server and emptying the cache:
But it's worth keeping an eye on to see how often it comes up.
Due to the manner of caching we are doing it's not feasible to expire cached URIs based on last access.
Additionally, many of these cached URIs are nonsense links that don't even resolve to anything other than a 404 in the archive (e.g.,
http://forum.biohack.me/index.php?p=/entry/register&Target=discussion%2F406%2Fwhat-do-you-feel-most-with-your-magnet-your-top-5%3F, which is a vanilla entrypoint that the rails redirect was never coded to handle).