hugenbdd

Yes There are two - Move All files. One that runs based on the cron entry in the configs that calls the original mover (from the original plug-in way back...). And another that is based off percentage used. Two different sections of code....

Looks right.. Can you enable logging and post the log entries? Then I can track down the issue.

@Squid What's the minor change you are asking for? (Just want to be prepaired for the plug-in if needed...)

Dooph! I'm still living in 2020 don't ruin my reality and don't tell me what happens in 2021.... Fixed...

New Release to fix this issue.

Great! In normal Linux dos2unix will take care of this. There is a "end of line" character difference between Windows & Unix. Sometimes they show ^M if you print the file from the command line.

Make sure logging is on. Move Now button follows plug-in filters (Yes) Turn on test mode (Very bottom) Test each directory one at a time in your file. It's possible there are control characters for the end of line if you created the file in windows. If you created it with vi editor or from the command line this should not be the case.

I think you will be okay... but make a backup of the file just in case.

Probably doesn't survive reboot. I'll work on a release in the next few days.

Please post in here. A Screen shot of your mover settings, set mover logging to enabled, and the diagnostics zip file mentioned above after mover has run. This should let me track down any issues.

There was an Echo in there for that statement. Next release will have it updated to follow the logging settings. (But that may be a while...) If you want to fix it now. Line 396 of /usr/local/emhttp/plugins/ca.mover.tuning/age_mover Change echo "mover not Needed." to mvlogger "Mover not Needed."

Make sure the file matches in here. /boot/config/shares

Looks like it might be a share name issue. Sep 27 19:05:59 unRaid root: mvlogger: Not in Test mode Sep 27 19:05:59 unRaid root: find: unknown predicate `-depth+= | /usr/local/sbin/move -d 1' Is the share name media or Media. (lower versus upper). Seems also maybe a configuration file may have a mismatch in it to cause the issue above.

I'll check the code but should only be happening when logging is enabled....

Mover Logging : Enabled. (Up top, schedule area) You can see in your last pic the "mover started. Mover Finished". at the bottom. That will expand to a lot more. You will need to browse the individual cache drive or use the console and issue ls commands on the cache. https://www.tecmint.com/15-basic-ls-command-examples-in-linux/ also https://www.techrepublic.com/article/linux-directory-navigation-tips-and-tricks/#:~:text=To change to your home,and then press [Enter].

And you probably want to set this to no. Move files off cache based on age?

Enable logging, then check what files are left. Do you have other shares using this cache drive? (i.e. appdata)

Try setting this to 0 and not 1. Move files that are greater than this many days old: You can also run in test mode and review the files it will be selecting. (see the log file)

Newer... Previously I had a separate button, but Squid gave me direction in how to add this back in so I added it as an option.

Forgot.. (I have to many options in the plugin....) But do you have this set? (Second to last question) Move Now button follows plug-in filters: Yes

Is it the button in the scheduler page that isn't working or when it is run at it's scheduled time? (Sorry, will play around with tonight/tomorrow)

Possibly. I don't have 6.10 yet. I'm still on 6.9.1 I'll update my dev box this week. What might have happened is that 6.10 provided a new mover script. Overwritting the plug-in's script which just points to the plug-in's new script or the original script. You might be able to get the plug-in working by removing then re-installing the plug-in.

Yeah those aren't good. I'm not very familiar with hard linking. But it should be moving them. Found this thread.. Looks like maybe the 2 dangling links are related to possible corrupt disk/files.

Please post your Diagnostics log file. Tools>Diagnostics>Download

Not from my plug-in. If you have a lot of experience you can create your own command line and pipe the output to the mover binary. Something like below in a cron entry. (User scripts plug-in). However... you won't have any of the supporting code around it. i.e. to see if mover is currently running. find "/mnt/cache/<YOURSHAREHERE>" -depth | /usr/local/sbin/move -d 1