This question may be related to a resolved thread.
Picking up on another thread that’s closed but not resolved…
Sue stated:
EE uses db_cache as a folder name, not db_cache_delete. Hmmm…
But if you look at delete_directory() in /core/core.functions.php
you’ll see the following:
mv {$path} {$path}_deleteSo the delete routine is adding _delete to the end of the directory name, so in fact EE could be creating a directory called db_cache_delete. But sue doesn’t see it in her screen shots because it is supposed to be immediately deleted.
Thought Fabrice P. would want to know!
Sue if you want to reopen that thread with Fabrice…
Now on to my (related?) problem:
I am seeing lots of the following errors in my error log:
mv: cannot move `/www/system/cache/page_cache' to a subdirectory of itself, `/www/system/cache/page_cache_delete/page_cache'
mv: cannot stat `/www/system/cache/page_cache/45b19e1a82cd4199fdbef449f8af0efb': No such file or directoryjust now I see:
rm: cannot remove directory `/www/system/cache/page_cache_delete/4c61b7f8e3c2ad350cd4821e9bde7b68': No such file or directory
rm: reading directory `/www/system/cache/page_cache_delete/668ef11a4e29cd5d609cb405033f86f5': Input/output errorThis is in Expression Engine 1.6.8.
The file system is mounted through an NFS. Permissions look OK to me, but permissions are not really my expertise.
If I had to guess on what is going on I would say that there is some latency in the mv command (or the filesystem), such that even though mv returns 0 (success), when the rm command kicks in the filesystem doesn’t know that the _delete directory exists yet! Haven’t studied the delete_directory() function carefully enough to totally understand it but this is my hunch.