hugenbdd

Good catch! I did not test this scenario. Will work on this the next day or two and put a release out to fix.

I'll look at that for the next release. I have been hesitant to change the code that move files to the cache. Just because I'm scared it will cause major issues when people fill up their cache drive by accidentally setting their media shares to prefer.

New Release ###2021.11.23 - Add GUI button in individual shares to move just that shares files from the cache. Must be cache yes - Fixed bug where original mover would overwrite syslog instead of append. Suggested from Tomr *Guess my wording could be a bit better. Basically sends all files on the cache pool name it find in the share path (example: /mnt/cache/TV) to the array.

Done. ###2021.11.23 - Add GUI button in individual shares to move just that shares files from the cache. Must be cache yes - Fixed bug where original mover would overwrite syslog instead of append.

I am game to add this to Mover Tuning. I can do the coding, etc. but... I'm not sure how to modify the page below. http://tower/Shares/Share?name=<SHARE_NAME> I would add a section with "mover" for the title/grey bar, and also two options. 1.) To enable the move per share on the share page 2.) Follow plug-in filters. If you can point me to someone that can help with adding the customization to the share page I'll start looking at it.

Looks like it's working as intended. Nov 15 15:50:44 Tower root: mvlogger: Checking to see if we should all files from share. Nov 15 15:50:44 Tower root: mvlogger: Move All Cache Threshold: 5 Nov 15 15:50:44 Tower root: mvlogger: /mnt/cache PCT USED: 31 Nov 15 15:50:44 Tower root: mvlogger: Pool /mnt/cache is above 'move all' percentage, moving all cache-yes shares to array Move All settings move everything in the share if it's on the cache and percent is above the Move All Cache Threshold.

There was some issue with it that was causing it to not move in the past. I fixed it, and tested as best I could... Move All from Cache-Yes shares when disk is above a certain percentage: Yes Move All from Cache-yes shares pool percentage: 10% That should move everything if the pool is above 10% (I would recommend this be above 60% or more if using it.)

Yes, can you post your log entries? I tried to test as best I could.

Update is out. (No more sizing of total files in test mode) Seemed to work with my changes, as I was only getting an error when in test mode. Please post your settings and the log entries if it still errors for you.

Think I was able to reproduce. Nov 11 21:26:33 Tower root: mvlogger: find "/mnt/cache/TV" -depth -type f -mtime +29 -print0 -e '.anchor' | du -shc --files0-from - | tail -n1 Nov 11 21:26:33 Tower root: find: unknown predicate `-e' Will look at this tomorrow.

Can you turn on logging and post the entries from the syslog? makes it easier for me to reproduce.

Hi Masterwishx I don't think this is a plug-in issue. This is a general mover issues. You would probably have better luck posting a separate thread with debug log attached.

Updated... had some issues with testing so there were actually 3 releases today.. Hopefully I didn't mess to much stuff up. I fully expect to have some issues, but I tested as best I could... ###2021.11.08 - Actually subtract 1 from the age of files for 3rd item in 11-07 release. - uncomment commented out eval string for mover. (To actually move files.)

Yup agree... Okay, will look at it again tonight/tomorrow.

New update fixing the two issues above. I hope removing the 0 from the days old drop down does not cause issues. However, setting it to 1 will move with a "find -mtime 0" now. 11-07-2021 - Updated "move all" code to fix wrong variable and script error. - Removed 0 from days old drop down - Updated age_mover to day - 1 to be able to move files 24 hours old instead of 48. (See post from captaincu on 11/3/2021)

Sent you a message with updated file to test with. Will cut a release if it works for you. (After looking into the find date issue above.)

Nov 4 21:31:33 WheelzServe root: mvlogger: /mnt/cache PCT USED: 86 Nov 4 21:31:33 WheelzServe root: mvlogger: Pool /mnt/cache is above 'move all' percentage, moving all cache-yes shares to array Nov 4 21:31:33 WheelzServe root: mvlogger: Not in Test mode Nov 4 21:31:33 WheelzServe root: find: unknown predicate `-depth+= | /usr/local/sbin/move -d 1' Nov 4 21:31:33 WheelzServe root: mvlogger: Complete Mover Command: find /mnt/cache/Media -depth Will look into this tomorrow morning. Could be an issue with the code, or could be an issue with the share config files.

Can you post the syslog entries with logging enabled for when it is not working?

Sorry for the late reply. That makes sense. I'll do some testing for the next release.

Sorry, can't help much here. Maybe try a simple script that echo's out to the sys log and see what happens. That section just calls the path that is put into it...

look to see what the config file is set to ls -ltr /boot/config/shares If it mis-matches (based on the case of the letter) then that is the problem. Else, maybe post your debug log files?

Yes I believe it's safe to rename the file with the correct case. You should make a backup of the file and store it somewhere else just in case though. FYI - This directory will list the files/shares. cd /boot/config/shares

I will be out for a few days and won't be able to look at the issues until Wed. evening at the earliest. The best way to get the settings you want is to set the plug-in to test mode and enable logging. Then review the syslog for the cache entries.

Plug-in still works. however... It's easy to set enough stringent configs that the cache does fill up. I agree, cache - prefer is the most common issue. Best way to check to see why a cache is filling up outside of cache-prefer is to run in test mode and review the logs.

I think you want to remove the "Force move of all files on a schedule:" (Set to no) And keep the settings for "Move All from Cache-Yes shares when disk is above a certain percentage:" Yes, your %. This checks to see if the cache is above your set threshold. If it is, it will move everything. Based on the scheduler. Looking back at your original question.. The plug-in just check's based on the schedule not based on the % used. Best way to follow this would be to.. 1.) Mover Schedul: Hourly 2.) Set your percentage to move files. (Only move at this threshold of used cache space: 20%) 3.) Set % to move all file if greater than your percentage. You will still have an "hour" delay between checking. But usually a large enough hard drive and combination of low enough threshold make this workable.