hugenbdd

How big do you need? I fear not moving large files will make it very easy for the cache to fill up quickly and cause problems.

It should be 1024M not kb. if you have 1024 selected the find will add a -size +1024M

Not sure why it doesn't show up. I was not able to find it on a search either. I'll reach out to Squid on the next release. if you want install the 6.9rc2 version, you can use this URL. https://raw.githubusercontent.com/hugenbd/ca.mover.tuning/master/plugins/ca.mover.tuning.plg

You Can. From the Plugin's tab, then "install plugin" put this URL into the textbox https://raw.githubusercontent.com/hugenbd/ca.mover.tuning/6c146ad3ad63d162488d7e965c011d48d3e47462/plugins/ca.mover.tuning.plg Then hit install.

Mtime https://www.unixtutorial.org/find-mtime-identify-recent-files-in-unix/#:~:text=as you probably know from,on when they were modified. Yes, you would have to list all other directories you don't want to move. Maybe put the directory you don't want on cache on it's own share and disable cache so it writes directly to the array.

Yes it will still work correctly. since you are on the version from may and in in raid 6.8.3. The warning is because the latest install log file has a minimum requirement of 6.9.0-rc2. But because you are on the older version you are fine. The “fix” will happen once 6.9 is out of beta.

We can't do read time because of the way unraid mounts the shares (Look back a few pages as the details are discussed). I go off of "mtime". The majority of what this plugin does, is change the "find" string to send to the mover binary. The stock mover script looks something like "find /mnt/usr/ | /usr/local/sbin/move" and I will change it to look something like "find /mnt/usr/ -mtime +30 | /usr/local/sbin/move" Yes you could use the "Ignore files listed inside of a text file:" setting, and put all the directories in that file you don't want moved off cache. As it adds a 'grep' statement in between the find and the mover. (<findstatement> | grep -vFf '$SKIPFILESLIST' | <mover binary>)

Ignore for now. If you have the old one from the archive raw link posted earlier.. you should be fine. (Which it looks like you do.)

That's odd. This file (/boot/config/shares/Share1.cfg) should of had the entry of shareUseCache="yes" inside of it. As I check to see if the share has a cache. for SHARECFG in /boot/config/shares/* ; do if grep -qs 'shareUseCache="yes"' "$SHARECFG" ; then echo "Share Config: $SHARECFG"

Can you post a pic of your schedule page or let me know what you have in the file ignore box so I can try and reproduce on my end.

Try now... I updated the install script.

New Version released. ###2021.01.08 - Added version check to Install script. - Removed threshold percent check in mover perl script. - Added threshold percent check to age_mover bash script. - age_mover bash script now check for global threshold percent or the a manual entry in the 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) - Removed cache disk check in perl script to remove warning on scheduler page. - Several hard coded echo statements to help in trouble shooting/debug. These will be removed later but may cause an email to be generated and sent to you.

Kizer It operates the same way (as the old one) However, in this beta... if ANY cache pool is over the percentage threshold then it invokes mover for all pools. (I plan to change this in the near future). Days old only comes into play once you hit a certain percentage used. It's possible that if percentage threshold is not hit, then your files on cache just keep aging until the percentage threshold is hit. I have a 2TB cache drive. I have my percentage used threshold set to 65% and 35 days... So TV/Movies stay on cache for at least 35 days. Sometimes longer if I had a busy download day in the past 35 days.... Just take note that if you don't have mirrored cache drives.. then your files are not protected by the array/parity drives. I am not worried as I backup to google drive nightly, and can just retrieve my files from there in case of a cache disk going bad.

Looks like you are on 6.8.3 Uninstall, then install the package with the URL below. https://raw.githubusercontent.com/hugenbd/ca.mover.tuning/6c146ad3ad63d162488d7e965c011d48d3e47462/plugins/ca.mover.tuning.plg

If you installed the old version from the link I posted this morning... then you should be able to ignore the message in Fix Common Problems.

I think you can re-install the old plug-in from May by going to the history of the github and posting this URL (May 11th version of the plug-in script) into the URL for install plug-in. However, I have not tried this. https://raw.githubusercontent.com/hugenbd/ca.mover.tuning/6c146ad3ad63d162488d7e965c011d48d3e47462/plugins/ca.mover.tuning.plg

Added, hope that fixes the "update" issue on 6.8.

something like this? (Saw it in your Community Apps plg..) $version = parse_ini_file("/etc/unraid-version"); if ( version_compare($version['version'],"6.9.0", "<") ) { echo "********************************************************************\n"; echo "\n"; echo "unRaid version 6.4.0 or greater to run\n"; echo "\n"; echo "********************************************************************\n"; exit(1); }

Where can I set this attribute? I don't see it in the plg file.

If you see an update in 6.8, do not update. This is for 6.9 RC2 only... I have a new version, but am working through some bugs. You can install if you want to test, but I foresee a few changes soon. https://raw.githubusercontent.com/hugenbd/ca.mover.tuning/master/plugins/ca.mover.tuning.plg Currently, I check all cache pools for their size, and if one is over the threshold it will initiate a move for all pools. I plan to change this to check each pool individually. But wanted to get an initial release out right now. Squid - Can you point me to any changes for the logger and how to check if cache exists? Currently, the mover.tuning.page file throws a warning that no cache exists... I would like to keep the check instead of just deleting it. if (empty($disks['cache']) || $disks['cache']['status']=='DISK_NP') { echo "<p class='notice'>No Cache disk present!</p>";

Got my second box up and running with RC2 and had a chance to review the code. There doesn't appear to be a lot of changes that I have to make. I'll be working on a release, but the holidays may slow me down a bit.

I would suggest removing the plug in, then moving everything. I'm working on getting a Dev box up and running so I can continue working on this for the new Beta.

I branched Squid's original mover and mine is now the one listed in Community Apps. I don't have a dev box to install 6.9 to. I am also in the middle of buying a house and moving. However, if someone can post the 6.9 mover script I will try and get the code ready to handle multiple cache pools.

I would suggest opening a new thread under general support and post your log files. There are several other threads dealing with similar issues with mover and it looks like it could be a number of possible things.

Start with the stock mover and see if you can move 20-40GB of data off the cache first without it locking up your system. Make sure logging is enabled. I do not have a separate logging file. After you have confirmed it doesn't lock your system up with the stock mover, then install the plugin and just start off with one or two settings.