I got a notification from FCP that I have files on my cache drive that haven't been migrated to the array. I have the mover scheduled to run because I got this warning. Initially it wasn't scheduled because I hadn't set up any of my shares to use the cache. I turned it on briefly for one share, then turned it off. I have logging enabled on the mover. When I run the mover, nothing is logged and nothing seems to get moved.

 

Here's the share showing files on the cache:

 

Here's the shot showing the mover set to log:

 

and here's the log showing the mover run:

Quote

Feb 10 16:05:59 Backup emhttpd: req (10): cmdStartMover=Move+now&csrf_token=****************
Feb 10 16:05:59 Backup emhttpd: shcmd (98362): /usr/local/sbin/mover |& logger &
Feb 10 16:05:59 Backup root: mover: started
Feb 10 16:05:59 Backup root: mover: finished
Feb 10 16:07:05 Backup emhttpd: req (12): shareMoverSchedule=40+3+*+*+*&shareMoverLogging=yes&cmdStartMover=Move+now&csrf_token=****************
Feb 10 16:07:05 Backup emhttpd: shcmd (98365): /usr/local/sbin/mover |& logger &
Feb 10 16:07:05 Backup root: mover: started
Feb 10 16:07:05 Backup root: mover: finished

 

I took the screen shot of the share after the two mover runs.

 

Any suggestions on what to do to get these files to actually migrate off the cache drive?

backup-diagnostics-20190210-1615.zip

Edited February 10, 20197 yr by FreeMan

That share is set to cache-no. Mover will only move cache-yes shares from cache to array, and cache-prefer shares from array to cache. Shares set to cache-no and cache-only are ignored by mover.

 

 

More about the devil in the details for the Use cache settings:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?page=2#comment-537383

 

So I need to set it to cache-yes, run the mover, then set it to cache-no to prevent new files from being written.

 

Got it.  Mover is running now.

 

Thanks!