[[6.9.2] Mover not moving]

Right!  Sorry about that.

 

I see what you meant on the other thread.  Thanks

[[6.9.2] Mover not moving]

@trurl

I re-read it... still not finding it.  From that link:

 

• If using the mover tuning plugin first thing to do is to check its settings or remove it and try without it just to rule it out.

  • I had the plugin removed

 

• use cache pool option for the share(s) is not correctly set, see here for more details but basically cache=yes moves data from pool to array, cache=prefer moves data from array to pool, cache=only and cache=no options are not touched by the Mover.

  • All share in question were Cache=Yes

 

• files are open, they already exist or there's not enough space in the destination, enable Mover logging (Settings -> Scheduler -> Mover Settings) and it will show in the syslog what the error is.

  • Were not open, did not exist (false error, in my opinion), more than enough space

  • Checked the logs, the only error was 'file exists' of which it didn't in the array

 

• if it's a not enough space error note that split level overrides allocation method, also minimum free space for the share(s) must be correctly set, usual recommendation is to set it to twice the max file size you expect to copy/move to that share.

  • Allocation method was not an issue

 

File Exists error... The issue that I have is the mover attempted to move the file, threw a file exists error when one didn't exist.  In my opinion, the error should have mentioned that the two shares in question had their cache drives set to two different pools.  Once I aligned the shares with the same cache pool, all was good.

 

 

 

[[6.9.2] Mover not moving]

Thanks for that.

 

Understood that it's a Krusder issue for when I 'move' from downloads to Plex...

 

But why did the Mover not move?  It would not move until I made Plex use the same cache drive.

 

Also - shouldn't this be updated to reflect the issue?: