kizer

When I export the log to look at it the times for the tests are no where near when they where taken. Is there a way to fix this or adjust the time zone?

Before reading this understand this is not meant as a poke in the eye, just some criticism from somebody or I should say something else. Lol Ran it thru some Ai and it said the following: This is a well-structured bash script for managing cache drive capacity on what appears to be an Unraid server. Here's my analysis: StrengthsClear logic flow: Checks threshold → stops containers → runs mover → restarts containers Safety mechanisms: Lock file prevents concurrent mover runs Flexibility: Configurable blacklist and start-priority containers Good logging: Echo statements track script progress Graceful container shutdown: 30-second timeout for proper stopping Potential Issues & Suggestions1. Lock file cleanup on failureIf the script crashes after creating the lock file but before removing it, the mover will be permanently blocked. Consider adding: bash # Add trap to ensure cleanup trap 'rm -f "$lock_file"' EXIT ERR INT TERM2. Array iteration vulnerabilityThe Containers variable isn't quoted, which will break on container names with spaces: bash # Current (vulnerable): for val in $Containers; do # Better: while IFS= read -r val; do # ... container logic ... done < <(docker ps -a --format "{{.Names}}")3. Blacklist/StartFirst comparisonUsing == without quotes can cause issues: bash # Current: if [ $val == $check ] # Better: if [[ "$val" == "$check" ]]; then4. Race conditionBetween checking if the lock file exists and creating it, another instance could start. Use atomic operation: bash # Instead of separate check and touch: if ! mkdir "$lock_file" 2>/dev/null; then echo "Mover already running!" exit 1 fi # Then at cleanup: rmdir "$lock_file"5. Error handlingThe mover command has no error checking. Consider: bash if ! /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start; then echo "ERROR: Mover failed!" # Send notification /usr/local/emhttp/plugins/dynamix/scripts/notify -i alert -s Docker -d "Mover failed!" rm "$lock_file" exit 1 fi6. Container state verificationAfter starting containers, verify they're actually running: bash # After the restart loops: sleep 5 # Give containers time to start failed_containers=() for val in $Containers; do if [[ $(docker container inspect -f '{{.State.Running}}' "$val") == "false" ]]; then failed_containers+=("$val") fi done if [[ ${#failed_containers[@]} -gt 0 ]]; then echo "WARNING: Failed to start: ${failed_containers[*]}" fiMinor ImprovementsAdd set -euo pipefail at the top for safer error handling Use declare -a Blacklist=(...) for explicit array declaration Consider logging to a file for troubleshooting: exec > >(tee -a /var/log/cache_mover.log) 2>&1 Overall, this is a solid script with good structure. The main concerns are around edge cases with concurrent execution and error handling.

I couldn't get this to work at first and even deleted it. I later revisited it and did some digging. In my case my files are stored at /Media/Movies and /Media/TV in the settings they displayed by default as: media/Movies media/TV it dawned on me that media might need to be Media for the plugin to work. Sure enough I changed the media to Media and it fired right off.

I personally use PlexCache along with Mover Turner. I add the exported list file and pathway from PlexCache into the Exceptions list of Mover Tuner and every morning it Caches files and updates the list and Mover Tuner ignores them until a media file is watched and Plex Cache removes it from the list and Mover Tuner moves it into the Array.

Not a direct solution to what you guys are looking for, but It is a starting point.

Gave this a run on my Backup Server knowing that I could easily restore anything that messes up. How often does it check to look at available space? I told it to move until I'm at 999GB when the drive was sitting at 994GB on a drive and it only had to move 5GB and now its 16 Movies in when I'm sure 1 or 2 would of been perfectly fine. I like how its keeping the time/date stamps on the files.

I know lots of people have always wanted something like this. Have you considered making this a Plugin? Also is there a possibility of baking in a dry run feature so people can test without actually moving files?

Jan 1 09:05:50 Tower kernel: XFS (md10p1): Corruption detected. Unmount and run xfs_repair Saw this in your syslog.txt file. I'd wait for more info from somebody a bit more knowledgable than myself.

I'm getting the same numbers carrying on forever. I'm running it on unraid 6.11.5. I still can't get it to ignore files in a list either on the newest build.

I noticed the ignore list isn't working on my machine either. Running the newest build for Mover tuner and 6.11.5 if that matters at all. When I run the original mover turner it does follow the ignore list.

We demand some photos of the old interface. I started using 4.2 What did the older versions look like? Please and Thank you of course. lol Started in 2009 and I see a long future with unraid.

I don't know much about Rockstor, but I do know if you install a drive into unraid it wants to clear the drive and start fresh. You can mount drives using the Unassigned Devices Plugin and see your drives/data, but they will not be in the protected array. From there you can move data around in and out of the array or simply leave unprotected.

Don't know if this will help you much, but its an idea. https://unix.stackexchange.com/questions/468500/creating-directories-with-sequential-numbering

I use the Backup/Restore Plugin which shuts down my dockers and then puts them on my Array in a Share Called CacheDriveBackup and then turns them back on. I also have it set to backup each docker individually so I can restore individual dockers if there is a need. I wrote a simple basic script so I can restore any tar file as needed when I need to restore an individual docker. I do not backup my docker.img at all. I can easily restore it simply by rebuilding it and installing my dockers.

Sure its a bit old screen shot, but here are my settings that I still use today. Keep in mind there might be an option or two not shown on this one, but I think its pretty self explanatory when you read the new ones. Just to clarify a thing or two. Every day at 5:45AM my system fires off the Mover script based off the unraid default settings. It looks to make sure that at least 5% is used and only moves files that are 20days old. The reason I did this was simple. I didn't want the script firing off every minute because in the past I noticed that when the script ran it was spinning up all my drives. No idea if that has been addressed, but doing it my way it doesn't matter because I have other things running at 6AM and these runs prior to. So after it fires of the script and verifies that at least 5% is used because there needs to be some kind of threshold set because its my understanding that it uses the threshold as the basis for triggering other things. If that was changed I'm covered either way. 😃 So now that I've set it to run everyday at 5:45 and at least 5% is used it looks for files that are Older than 20 days and moves them.