I have files that stay on the cache drive while others are moved. Here is the log.

 

TRIED: Rebooting. Did not work

          I removed the files from the share, then re-copied them back in the share . Then invoked the mover. Did not work

          I added a random file to that same directory to see if that would be moved. The random file was moved but not the others.

 

log.txt

Do the files that you're waiting to move have a version (or file with the same name and location) exist on the Array!? I.e on a a"Full" disk!? Remember there might room on an Array but have full disks. If so then Unraid will try and overwrite that file and if there isn't enough space on that disk (not the overall share) then I think it will fail. The way around it I think would be to move that file to a disk with more space then execute the mover again and I think it would work. Or you could move some files from that disk to increase the space enough to let the overwrite happen.

 

Also - remember to check the "min free space" variable for disks. This is the min free space required before the disk is considered Full. Ie if it is set to 30GB at least that much needs to exist to copy to the disk.

 

Hope this helps.

Have your read this section of the unofficial manual on 'Min Free Space' and the next section on 'Split Level'? 

 

    http://lime-technology.com/wiki/index.php/Un-Official_UnRAID_Manual#Min._Free_Space

 

These settings are independent of each other and either one can cause the problem you are having.  The Split level seems to present the biggest problem for many folks to get a good handle on what it does and what the appropriate setting should be.  It can be set to 999 which is such a high value that it never comes into play.  However, it can cause problems if you store DVDs in file-and-folder format (rather than in ISO format) as the .vob files can then be split across multiple disks. This can cause the playback to 'pause' (or 'stall') if the next .vob file is on a disk that has been spun down.

Thank you for that link. It was helpful in understanding the whole Min Space, Split Level phylosophy... lol

 

But it took more thinking on my part. I found that the files not being copied were partially copied to a FULL disk. So I proceeded to erase these pesky files from the share (FILMS) {Yes I had a copy } This was, as I so thought, suppose to remove the partials from the FULL disk and also from the CACHE disk. Well, the partials were still on the FULL disk. So I erased them directly from the disk.

 

Now I felt I could re-copy them from my backup back into the array and have everything working fine. Not ! I invoked the mover and found the same error, it was trying to place the file back on the FULL disk. (Note. The FULL disk is indicated as haveing 0 free space, by unRaid.)

 

I did check and re check my share settings.. Could not come up with a reason why this was happening...

 

ANYWAYS

 

SOLVED By re-doing the above steps BUT before invoking the mover I set the share to EXCLUDE the FULL disk. That did it for me.

 

 

Now I felt I could re-copy them from my backup back into the array and have everything working fine. Not ! I invoked the mover and found the same error, it was trying to place the file back on the FULL disk. 

Now I felt I could re-copy them from my backup back into the array and have everything working fine. Not ! I invoked the mover and found the same error, it was trying to place the file back on the FULL disk.

You need to check the full disk to check there is not already a file of the same name there?  If a file already exists on a disk then unRAID will overwrite it rather than use a different disk.