It looks like Linux is funning a FSCK disk check and is attempting to delete unused Index Nodes in the wfcache folder.
any idea why there are unused index nodes in wfcache?
File systems are complex and can become damaged. The OS then tries to repair the directory structure. That’s what it looks is going on to to me in that directory. Are you having any problems with Wordfence caching otherwise? Here is more info on inodes…
http://en.wikipedia.org/wiki/Inode
That’s the main problem we have in Wordfence caching. Cache can’t be deleted because of the deleteD/unusued inodes to cache files.
Since this happen twice w/ a fresh VPS and only for wfcache folder, we suspect this issue is related to wordfence caching.
Are you able to clear the Falcon cache using the built-in clear function?
http://docs.wordfence.com/en/Falcon_Cache#Clearing_the_cache
We were able to clear cache after fsck fix the file system error. But the problem we want to avoid is on deleted/unused inodes.
Are things normal after deleting the cache? FSCK is doing it’s job by locating unused inodes as file systems are always in need of cleaning and repair. This looks pretty normal to me. May just be coincidence that the cache folder has come up twice in the scans. Keep an eye on it and let us know.
Thanks,
Brian
we are forced now to use other caching plugin because of the problem w/c we don’t want to encounter again.
thanks Brian
Hi there,
Brian is correct in his assessment, but he’s asked me to investigate too. This is unrelated to Wordfence. To be clear, if you haven’t fixed the cause of the problem, you will see it in the next caching plugin you use and will probably start to see it corrupt operating system files. Basically you need to urgently find the cause and fix it or you’re going to have a very problematic system.
I’m marking this resolved. I’m going to assume you’re going to investigate why your OS filesystem is experiencing corruption and fix that, then move forward and if you have any further questions related to Wordfence specifically please don’t hesitate to start a new threat and Brian or Tim will be happy to help.
Regards,
Mark.
