hugenbdd

Let me introduce you to Mover Tuning.... Then open your wallet for a very large SSD drive to take the most advantage of spinning down drives.

Partially To do it right, it would take some effort. I can't just check the share size, but have to check each drive for the share, then add up it's size on disks. And after that, then I can only throw an error to syslog and then not "move" any data.

Yes works with multiple pools. Gotcha's? 1.) Try to avoid spaces in share or pool names. 2.) All fields from gui are applied to all pools. i.e. it's all the same. with one exception at the moment. 2a.) You can specify a different percentage per pool. Create an entry in ca.mover.tuning.cfg file. (example: /boot/config/plugins/ca.mover.tuning cachetv="65") - "cachetv" being the name of the pool. - if using single digits leading zero required. (i.e. cachetv="01" for 1 percent) 3.) I plan to expand this type of entry for a few other fields in the future. 4.) As with any share setting, be very careful when setting cache-prefer. Several posts where users are filling up their cache drive when using that setting.

###2020.05.06 - Added 0 to options of days old. (Will move anything greater than 24 hours old) - Added 6,7,8,9 to options of days old. - Increased days old limit to 765 - Removed "Original Mover" button after paypal donation link. - Added "Move Now button follows plug-in filters:" to make "Move Now" button run based off of plug-in settings (Yes), or run original mover (No). - Moved some code around in mover.php so ionice would be initiated. - Updated mover code for moving from array to cache (generally cache-prefer) to follow Squid's update on 4/11/2021. (Fix for shares with space in their name) **********CAUTION**************** Move Now button now calls unraids original move now code!!!!! It will move almost everything, to change set Yes to " Move Now button follows plug-in filters:" (Last question in section) Future Changes: Add an option to invoke original mover (i.e. everything) if percent used reaches a user selectable percent. (Must be higher than the entry for "Only move at this threshold of used cache space:")

I can add some more single digits. Working on some back-end changes. Will be a week or two before I get the next release out.

So I am clear with the tuner, the mover settings schedule (set to daily) just invoke the mover and then the mover tuning settings get looked at to determine whether mover does anything, right? Currently - This will likely change soon. I plan to make the button have the option of using default unraid mover, or to follow the settings. (Just working on initial code now based on Squid's recommendation). Logging - Depending on the version, Logging might not have been "created". Not sure it's worth going back and looking for it. I have logging sorted out now so users can at least enable it and give me a good idea of what/where might be failing.

0% is working for me. Can you do the follow. 1.) Verify you have the latest version installed. (2021.04.20) 2.) Settings: Mover Logging: Enabled 3.) Screen shot of your settings page. 4.) Post the section from your log file that looks similar to this after it runs. Apr 27 08:35:48 Tower root: mvlogger: Age supplied Apr 27 08:35:48 Tower root: mvlogger: Size supplied Apr 27 08:35:48 Tower root: mvlogger: Sparness supplied Apr 27 08:35:48 Tower root: mvlogger: No Skipfiles Argument Supplied Apr 27 08:35:48 Tower root: mvlogger: No Skipfiles Argument Supplied Apr 27 08:35:48 Tower root: mvlogger: No Before Script Argument Supplied Apr 27 08:35:48 Tower root: mvlogger: No After Script Argument Supplied Apr 27 08:35:48 Tower root: mvlogger: CTIME Argument: no Apr 27 08:35:48 Tower root: mvlogger: *********************************MOVER START******************************* Apr 27 08:35:48 Tower root: mover: started Apr 27 08:35:48 Tower root: mvlogger: No Script to Run. Apr 27 08:35:48 Tower root: mvlogger: Share Name Only: Backups Apr 27 08:35:48 Tower root: mvlogger: Cache Pool Name: cache Apr 27 08:35:48 Tower root: mvlogger: cache Threshold Pct: Apr 27 08:35:48 Tower root: mvlogger: OVERALL Threshold: 0 Apr 27 08:35:48 Tower root: mvlogger: Share Path: /mnt/cache/Backups Apr 27 08:35:48 Tower root: mvlogger: Pool Pct Used: 60 % Apr 27 08:35:48 Tower root: mvlogger: DFTPCT LIMIT USED FOR SETTING: 0 Apr 27 08:35:48 Tower root: mvlogger: Threshold Used: 0 Apr 27 08:35:48 Tower root: mvlogger: Skipfiletypes string: find "/mnt/cache/Backups" -depth Apr 27 08:35:48 Tower root: mvlogger: Complete Mover Command: find "/mnt/cache/Backups" -depth | /usr/local/sbin/move -d 1

Lots changed because of multiple cache pools. I will test having 0% used and no other settings, but it should work. (Might take me a day or two)

find "/mnt/cache/share1" -depth -cmin +60 | /usr/local/sbin/move -d 1 The find command just creates a list of files matching your criteria. <-- This is basically all the plug-in is doing, creating a long custom find command. "/mnt/cache/share1" - /mnt/cache <--would be your cache pool name. If you don't have multiple and have not renamed it, then it should have defaulted to cache. /share1 <-- is the share that have any files on it. Usually this would be TV or Movies, etc. These shares usually have "yes" to the question of "Use cache pool (for new files/directories):" in their share page. | <- Pipe, just telling the command line to send the output of the find to the move binary. /usr/local/sbin/move -d 1 <-- default move binary supplied by unRAID. If you create a custom command, I would suggest also looking to see if mover is already running (i.e. check for the pid)

Yup

Correct. if Drive Space used greater than 50%, find file's greater than 30 days old and send them to the mover binary.

No there is no either or for those options. The percentage is the first general overall check. If the cache/disk is not greather than the percentage set it basically exits for that cache drive.

I'm maintaining it. Set one option, then hit apply. Refresh the schedule page and then try and set your options. There is a bug on the first install/selection of settings (first time page loads) for why things are grayed out. I have not tried to troubleshoot it as there is an easy work around.

it's based on days. I don't think many would use hours. You could modify age_mover where ctime is created in the "find" string.... Or you could create your own mover command and put it in cron. # find "/mnt/cache/share1" -depth -cmin +60 | /usr/local/sbin/move -d 1

I'm not familiar enough with the base pages of unRAID to change them. The "original" move now is on the schedules page, bottom right. Just right of the donate button.

Cron Schedule to force move all of files: - Runs original mover on a schedule if you want all files moved. Only move at this threshold of used cache space: <-- set to 0%. This way if anything at all is on the disk, it should trigger a move and not put any "filters" on the find command. With all the options I have, you can usually find a way for it to work for your needs.

Install, go to the Scheduler page, select your schedule (Hit Apply under Mover Settings), then set at least one item in the mover tuning setting (Hit Apply under Mover Tuning w/Age - Days Old)

Hi Can we get a check for this file if Mover Tuning is installed? /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg Unless that file is not supposed to persist. It seems that maybe updating to 6.2 is removing the file. I have not updated just yet (will this weekend to verify) Thanks

Nope. If anything I would rather it go to Squid. I think the donate button in the settings goes to his paypal.

New Release 2021.04.20 Added "CTIME" option under Age. This allows the "find" command to use ctime instead of mtime. But, thinking I might need to tweak it again to remove the +.... (Please confirm if you use this option) Example find command: find "/mnt/cache/Backup" -depth -ctime +30

Can Klainn rename his to lower case to match the display name? Will there be any issues from doing that?

Can you do an ls -ltr of this directory? /boot/config/shares I think we should reach out to unraid and see what they might suggest. If shares should "EXACTLY" match their display names. i.e. caps or not. My guess is that it should match exactly.

Can you tell me what you have in this directory? /boot/config/pools/ Original mover loops through config files like this # Check for objects to move from pools to array for POOL in /boot/config/pools/*.cfg ; do for SHAREPATH in /mnt/$(basename "$POOL" .cfg)/*/ ; do Where my mover loops through shares. (like this) for SHARECFG in /boot/config/shares/* ; do if grep -qs 'shareUseCache="yes"' "$SHARECFG" ; then My gut reaction is that the file Personal.cfg should be renamed to personal.cfg. however, I'm not sure what impact that will have on your shares. Everything should be case sensitive.

New Update 2021.04.16 Added "Script to run before mover" text field. Enter the path to a custom script to run before mover starts. Added "Script to run after mover" text field. Enter the path to a custom script to run after mover finishes. These will ALWAYS run, even if the filters remove all possible files. i.e. "Mover not needed". I plan to change this in the future to only run if something is found. But that is months away at the earliest. Should probably stay away from spaces in the path/filename. I only tested with a simple "Hello World" script. next up, adding Ctime/Mtime option.

At the moment, it would run before doing any checks at all. In the future, if mover changes like I think it will, then I can incorporate a running of the scripts if or not depending on if something moves.