March 6, 20215 yr Hi All, So I've just logged into my unraid GUI and noticed 5 hours after schedule my move is STILL running. It's schedule is 7:30am AEST each day. Poking about by exploring into the share explore items I can see that it's moving shares that is marked as 'Cache Prefer' to the array. My single XFS cache drive would have been about 60% full when mover started, and we are talking appdata included here. Poking about in the shares, looks like it's not moving Cache - Yes items to the array at all, instead seems to have reverted to thinking that 'Cache Prefer' needs to be moved? I am using the Mover Plugin with the below config on v2021.03.03, but I only use this to exclude xml and pdb files from mover. I upgrade to 6.9.0 last weekend and have 3 days uptime, so no idea why this is only happening this morning? adam-htpc-diagnostics-20210306-1247.zip Edited March 6, 20215 yr by deanpelton
March 6, 20215 yr Community Expert Have you turned on mover logging to confirm what files are trying to be be moved? looking at the diagnostics I would expect the system to be trying to move appdata files from disk2 to the cache as there is space on it and that share is set to “use Cache = Prefer”.
March 6, 20215 yr Author Appdata was already on cache, the mover was moving it to disk2. I've just used midnight commander to move everything back to the cache and switched on mover logging. Restarted mover for a quick moment and attached the logs. Hesitant to let it run too long, in the 5 hours it was moving it moved my whole plex appdata to the array, as we all know, that directory is a nightmare to move. As you can see from the logs, the mover immediately started to move appdata back into the array. adam-htpc-diagnostics-20210306-1623.zip Edited March 6, 20215 yr by deanpelton
March 7, 20215 yr Author Hi Squid, I didn't realize it was CA mover until this arvo, happened around the same time as installing a bunch of stuff and upgrading. I'll do a post over in the CA mover threat with all the details.
March 7, 20215 yr Looking into this today. At first review it appears it does not like share's with a space in their name. Share Config: /boot/config/shares/TV Shows.cfg Should be a fix I can get out tonight.
March 7, 20215 yr New release available. Fixed the issue with a space in the share name. Also it checks to make sure it's not doing a find on the default "/mnt/cache". Code will just "exit" that specific move command in the loop. So this should not move anything under a defaulted /mnt/cache path in the future if it runs into a naming issue.
Archived
This topic is now archived and is closed to further replies.