MILDEW

I just came back to edit my comment after noticing the update. Thank you.

Has this been implemented, as of Unraid 7 beta 4??

I am still having an issue with Mover not running with this plugin. I have done some testing with diagnostic logs. These tests are all in one consecutive run after reboot. My first test was after reinstalling plugin and rebooting. I invoked "Move Now button follows plug-in filter", applied, and attempted invoke Mover via button. After clicking, it would immediately return to its previous state. Seemingly without running Mover. I believe I attempted this 4 times. I then reverted "Move Now button follows plug-in filter" to its previous state and invoked mover via button. I then successfully invoked Mover via WebGUI button and pulled diagnostic logs. towerone-diagnostics-20240414-1305 [test_one(fresh start-set_tune_to_buton_&_it_stopped_immediately-disabled_tune_filter_with_button_&_it_worked)].zip My following test started from previous state. I then invoked "mover stop" via terminal, invoked the "Log when not moving due to rules" option via Tuner, and repeated previous test by attempting to invoke mover via WebGUI button. Results were the same. I again pulled diagnostic logs. towerone-diagnostics-20240414-1313 [test_two(same_as_previous_but_ran_mover_stop_then_turned_on_tuner_logging-still_same_outcome)].zip My final test began where the previous left off. I toggled "Only move at this threshold of used cache space" from 0% to 5%, applied, changed it back, applied, then I invoked mover via the "Force move of all files on a schedule" option. This resulted in he Mover button greying out and Mover "running" seemingly without ever moving files. If let sit long enough it will have a random read with a much higher write (reads in double digit KB/s and writes much higher in the triple digit KB/s). I then pulled the diagnostic log. I have watched this same action previously for hours, and am again watching now. The only time it stops is with a Mover top command. The array_cache never gets smaller and the array never gets bigger, even if left to sit for days. I have done this test several times over the last week or so. Toggling "Only move at this threshold of used cache space" had no relevance, but thought I would mention it as I happened to do this time that had the same outcome as not doing it. towerone-diagnostics-20240414-1324 [test_three(again_same_as_before-toggled_5_&_0-started_with_cron-said_running_infinetly-no_movment_except_few_random_KB_with_higher_w_than_r)].zip If anyone can help me with this I would be grateful. I removed my previous comment, as this is likely better written and I previously didn't get any response.

This may only be a me issue; after updating to Unraid 6.12.10 this plugin has seemingly disappeared from my system and the App Store. If anybody has any insight on this please let me know. I don't remember anything in the changeling and it missing from the App Store has me quite perplexed.

@Squid I've noticed this also makes the "mover start" command follow this "filter" (including script execution when enabled). This is extremely helpful as I call for mover to start/stop on regular occasions. As it doesn't execute scripts and I have to account for this anytime I invoke "mover stop" by either including it in my calls or by running my mover scripts manually. It's a bit of a headache at times. Is there anyway you would be willing to do the same for "mover stop" that you did for "mover start"?? I realize this may not be as helpful to most. I just wanted to ask as it may be helpful to some.

I absolutely do.