April 16, 201412 yr I was checking my logs today and noticed the mover script ran this morning (like it's supposed to do daily) and moved a bunch of files. The problem is most of them were copied to the server on the 11th. And today is the 16th. I went back through the log and mover ran every morning like clockwork on all the days in between, but for some reason missed everything that was there till this morning. No errors in the log anywhere about anything. One thing to note, and it may or may not be the issue, is that I added a drop_caches command before and after the mover runs as is noted elsewhere in the forum to help with memory consumption with cache_dirs. That's the only thing I've done. Just for clarity, this is what was added to the mover script right after "mover started" and before "mover finished" # Let's dump caches echo "dumping caches" echo 3 > /proc/sys/vm/drop_caches I saved the new mover file to /boot/custom/mover and added this to my go file: #Remove mover script and then link to custom version rm /usr/local/sbin/mover ln -s /boot/custom/mover /usr/local/sbin/mover Does anyone think any of the above could be the issue or is it possibly something else? I can post the syslog, but it shows absolutely nothing as far as errors. Just shows the mover running each time. Thanks in advance.
April 16, 201412 yr Author Is the mover currently working correctly? Other than not moving files that were on the cache drive for 5 days, yes. But it should have moved them on the 12th I believe based on timestamps when the files went up, oldest was on the 11th (morning time).
April 16, 201412 yr Author If the mover is working then there is nothing to fix. So no explanation as to why it ignored files for several days than moved them? I'm just trying to understand this. I have it set to run daily and it runs daily, but it failed to move anything for several days. Why? I have it set to run daily on purpose to I'm not needlessly taking up space on the cache drive which has limited space anyway.
April 16, 201412 yr Author Did anything have those files open? Torrents? Shouldn't of. I'm using BTSync to keep files synced between servers and that last sync on one my shares was on the 11th. Now, I have no idea if it kept something open, but it certainly shouldn't have. I'm only syncing locally anyway.
April 17, 201412 yr Author I had a file move over this morning after mover ran so it wasn't picked up. I checked to see if the file (or any file) was open in my media directory and wasn't. So I ran it manually and it moved over fine. I'll check on this daily now and see if I can find the culprit if indeed it is an open file issue.
Archived
This topic is now archived and is closed to further replies.