hugenbdd

It should still work with the plug-in settings. It will not act as the original mover worked. I will test this afternoon as my mover is running now.

It does not replace the button/functionality on Main or on Scheduler where you set the time. That will still look at the settings for the plug-in. This is just calling the original "Move Now" code (now called mover.old under /usr/local/sbin) as if you didn't have the plug-in. So if you share is cache only, the original move should not move it. I added "Caution - Moves Everything" as more of a warning. Probably could have been worded better, but didn't want to put to much in the button. As I was just trying to give the original functionality back somehow.

03/17/2021 - New Release Add's an "Original Move Now" button. (Bottom right of the "donate" buttons" removed echo statements. I may add a button in the future to enable the button by a checkbox in the config settings.

It's because I left ECHO statements in the script. These help me catch bugs for the new release. I will release a new version in the next few days that will comment out the echo statements.

Should not be an issue. adding to cron is a bit different in unRaid. I can't remember the way they recommend. However, you would want to add something like /usr/local/sbin/mover.old start Maybe someone else on the thread can give you more specific cron instructions.

Haven't forgotten about this. Will circle back in a few weeks once things settle down with the new release and try and add this in.

It looks like your share is using a capital D, and the cache directory is using a lowercase d. It thinks they are two different directories. This needs to be corrected so that they match. once they match the plug-in will work. (Same case D) The original mover worked, because it does not try to match the share name with the cache directory and just moves everything.

Correct. I'm looking at adding a button on the page to call the original mover. You can still call the original mover from the command line. /usr/local/sbin/mover.old

You will want to call the old mover. /usr/local/sbin/mover.old

Looks like it should be working. Odd. It's almost like the cache directories got moved somewhere else or renamed. As it is throwing that find error with "no such file or directory". Maybe with the addition of cache pooltwo it got renamed with a capital Cache instead of lowercase cache? Can you run these two commands from the console? ls -ltr /mnt/cache find /mnt/cache/Downloads -depth -This will probably fail, like it did in the logs. We need to find the correct path and then I can see why my code didn't work correctly. Alternatively, you can go back in, set the "Downloads" share cache to something else, hit apply, then immediately set it back to the original cache, set apply

This is expected behavior. Just for clarity. When hitting the button, mover will run, however, the cache threshold may not be met, so it doesn't move anything and "skips" the custom mover command. (Check the logs to see the statements) I will look at putting a new button in, that calls the original mover. (This would not look at any of the config settings.)

New Release Allows for the custom mover to be invoked if the cache threshold ONLY is set in the config.

I changed where the percentage was looked at in the code. It used to be looked at before that if statement in the php file. But now it's in the new mover bash script. Needed to do this so it can handle multiple pools now.

Looking at the code... It does have to have "age" or some other config selected. if ($cfg['age'] == "yes" or $cfg['sizef'] == "yes" or $cfg['sparsnessf'] == "yes" or $cfg['filelistf'] == "yes" or $cfg['filetypesf'] == "yes" ) I'll look at this and update the IF string to look for percentage. Might be a few days though.

That's good. Appears that it's not reading your config file for the mover for some reason. Config file location: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg please cat that file for me. Should look something like this. root@Tower:/boot/config/plugins/ca.mover.tuning# cat /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg moverDisabled="no" moverNice="0" moverIO="-c 2 -n 0" threshold="55" age="yes" sizef="no" sizeinM="1" sparsnessf="no" sparsnessv="1" filelistf="no" filelistv="" filetypesf="no" filetypesv="" parity="yes" enableTurbo="no" logging="no" force="no" cron="" forceParity="yes" daysold="30" And just incase it's a permissions issue, here is how mine looks. -rw------- 1 root root 283 Mar 7 13:39 ca.mover.tuning.cfg Maybe try and change something in your config. Say threshold of 75% to 70%, then hit apply, and also change the "time" that mover runs and hit apply.

Can you run these two commands from the console? ls -ltr /usr/local/emhttp/plugins/ca.mover.tuning/ cat /usr/local/sbin/mover

Can you post your logs and scheduler settings? By design, it will start based on the scheduler, it just uses the setting to determine if anything moves.

I don't think it was. I'll review the test case and try to reproduce tonight or tomorrow.

Root Cause: Bash code didn't like the space in a share name. "TV Shows". Fix: updated code to handle spaces in the share name. Added: Check to see that the default "/mnt/cache" the codes uses if it cant find sharepoolcachename in the config file is empty. it will "exit" the mover try for that specific share. New Release available.

Yes that directory persists.

I tried to recreate with your Config1.xml path. (Minor change, I use Backups for my sharename..) Can't reproduce it. Maybe try my file ( I changed to Backup, to match your path), but place it in a different area? (/usr/local/emhttp/plugins/ca.mover.tuning/moverignore2.txt) moverignore2.txt

Version: 2021.03.03 Added a check as described above. Please update and let me know if you have any issues. I still have some plans to clean up some new potential issues.

Working on an update. Should have something released tonight. If your share config file does not have a "shareCachePool=cache" or another cache pool entry, then it was failing. Temporary fix would be to change each share to "none" than back to "cache", and hit the apply button, so the entry gets put into the config file. My update will set default cache name if it's missing in the config. brentdog, will circle back after the release tonight.

No, it will "error" out if you try to install that release on 6.8 as it checks the version now. For 6.8, follow this post.

Few things. There might be a hidden ^M character in your exclusion file if you created/edited it in windows. Either remove inside vi editor, try dos2unix (may not work in unraid), or sed -e "s/^M//" filename > newfilename Try just the find command on it's own from the console and see what it returns. (It should not have the files in the exclude file in the output). find "/mnt/cache/Backup/" -depth | grep -vFf '/boot/moverignore.txt'