hugenbdd

I could not get it working again after some of the more recent 6. releases.

@Swarles and yourself are welcome to take over this plug-in. I have not been able to spend the time it needs on it recently.

Can both update this file and let me know the results? I have updated it locally, but am not having the issue. File Location: /usr/local/emhttp/plugins/ca.mover.tuning/ Permissions should be 755 (chmod 755 age_mover) if they are not. (rwxr-xr-x) age_mover

Are you on ZFS or just a traditional cache pool?

Thank You WIll keep an eye on for when 6.13 is released and try to get an update out quickly when it is.

I will look into it. but.. I have been very busy with Family and work the past 4-5 months and the next few look busy also. I also have a few other issues to look into.

the mover.old file is so that we can restore the original mover binary. The location changed several releases ago but I'm not certain what version. If we remove this then it will not work for older releases. I will try and work on a way around this to satisfy older and newer releases this week. Which I think will be a "longer" if statement, and to check for the file before mv'ing it and also creating another if to create a copy for the sbin location file.

Could you post a screen shot of your settings? Could be due to Priority for mover process or Priority for disk I/O, something may have changed with those in this release.... But I won't know till I get a chance to test more.

I just installed 6.12.8 this morning. I will keep an eye on my transfer speeds.

Okay, I'll look at it closer when I get a chance. Currently, because I do not know how the unRAID binary is moving hardlinks, I just pipe the whole filelist into the mover binary and it takes care of it. As opposed to the file list looping through each one (for non hardlinked).

Is this something we could incorporate into the general plug-in to change the way we handle hardlinks today?

Should be able to call it from the command line. "SoftStop" tries to stop the mover once the current file has been transfered. (i.e. the code checks to see if softstop was triggered before moving to the next file in the list.). As long as you are not using hardlinks. Hardlinks does not loop through a filelist to move files but rather sends the full filelist to the binary mover file. root@Tower:~# mover status Log Level: 1 mover: not running root@Tower:~# mover stop Log Level: 1 mover: not running root@Tower:~# mover softstop Log Level: 1 Soft Stop Requested mover: not running root@Tower:~# mover start Log Level: 1 mover: started mover: finished

New Release thanks to @Swarles ###2023.12.19 - Change "while read" lines in age_mover to "while IFS= read -r" to fix trailing white spaces (Swarles) - Fix where sometimes mover would not run to mover.old scrip (Swarles) - Log if "share.cfg" doesn't exists to help trouble shooting (Swarles) - Check for ca.mover.tuning.cfg file and additional logging. (Swarles)

I believe it should have always been /mnt/cache and not the sharename. At least that is how I coded and tested it. If sharename/file.txt was working, I don't think it was intentional.

Mover location was changed somewhere between 6.9 and 6.11. So older versions still need an older path, hence the "missing". Once you run mover it creates a soft link. If you search back several pages I think I posted how to create the link. Will still go missing on bootup though. DM me if you can't find how to create it.