EDIT: TLDR - How can I apply different Mover features from the Mover Tuning Plugin on a per share basis?

 

Hey everyone,

This obviously isn't a standard request, but I am hoping someone might be able to help me come up with a good solution. I am wanting to have a media folder for my Jellyfin which is cache-->array so media files are stored on the array after being downloaded (but only when the mover runs). However, for simplicity in managing the media folder I would like to store metadata, artwork, etc in the folder with the media. This keeps it all together and also means I could in theory host another Jellyfin instance from a different computer, without having to download metadata again.

 

BUT...I don't want the array to spin up every time a user accesses the server simply to provide artwork. It would also load much faster on my cache. Ideally I would find some kind of solution where the mover does not move certain files (e.g. .jpeg, .svg, .nfo, .mp3) in this particular share from the cache to the array. 

 

I do understand I could simply not store artwork in the media folder, which I will do if there is no solution for my outlined problem. The primary reason I want to try to achieve it the way I suggested is because I use a theme song plugin for Jellyfin and this must store the .mp3 in the media folder for Jellyfin to find it. This would result in the behaviour of the array being started every time a user automatically loads a theme song, which is not ideal. I don't want the array to start unless a video file is being loaded.

 

BONUS QUESTION:
Is it possible to get Mover behaviour (on a specific share) that only moves files that are X days old? This could allow the cache to serve recently downloaded content (more likely to be accessed) faster and without starting up the array.

 

Thank you for taking the time to read through this

Edited June 15, 20233 yr by Swarles
Added TLDR.

Have a look at mover turning plugin

18 minutes ago, SimonF said:

Have a look at mover turning plugin

Thanks for pointing this out, I did download it earlier but quickly dismissed it because I thought it applied the mover to ALL shares.

Do you know if it is possible to apply different profiles to different shares? Or any other way I might be able to achieve that? 

 

I would love to be able to have all my other shares behave normally.

45 minutes ago, Swarles said:

Thanks for pointing this out, I did download it earlier but quickly dismissed it because I thought it applied the mover to ALL shares.

Do you know if it is possible to apply different profiles to different shares? Or any other way I might be able to achieve that? 

 

I would love to be able to have all my other shares behave normally.

Sorry I dont know @hugenbdd would get able to answer

No, settings apply to all shares.  The only one that is share specific is % of disk used.

 

I need some help with setting up gui pages for share specific settings.  I would like to be able to provide this, but it is most likely a ways off. 

 

You could accomplish this by looking at the plug-in code and writing your own bash script.

36 minutes ago, hugenbdd said:

I need some help with setting up gui pages for share specific settings.  I would like to be able to provide this, but it is most likely a ways off. 

I was thinking about what might be an ideal way to set this up and believe that the "scheduler" Mover Tuning setting could be a universal setting for each share and then in "Shares>[specific share]>Mover Tuning" is where individual share mover settings could be overwritten.

From my understanding, this only appeared after I installed the plugin?

I don't know much about development, but might try to take a look to see if or how this would be possible.

 

41 minutes ago, hugenbdd said:

You could accomplish this by looking at the plug-in code and writing your own bash script.

I will definitely take a look at this and try to create a script that meets my needs.  Although I suspect there may be issues even if my script moves only the files types I want off the cache and onto the array, because then the universal mover will run and move them onto the array anyway? I'm not sure if I can disable it for a specific share? I may be able to set the share to cache only, and manually move files to the array but I'm not sure how this would impact the system that unraid uses to direct traffic to the correct drives using a single path (I forgot the name).

 

Regardless, thanks for your help

Normal mover scheduled would move them, I'm not sure if there is a way to ignore whole shares.  Mover Tuning was originally written when there was just one cache drive, making it much easier... Now there's lots of intricoes to figure out. 

Yes, that is part of Mover Tuning.  meant to make it easier to empty a share from cache.

15 hours ago, hugenbdd said:

Normal mover scheduled would move them, I'm not sure if there is a way to ignore whole shares.  Mover Tuning was originally written when there was just one cache drive, making it much easier... Now there's lots of intricoes to figure out. 

Yeah for sure!

I'm trying to read up and understand how the Mover works, I know very little about linux/bash programming but in general given enough time can figure things out. Do you know of any good explanations or code where I can understand how the underlying Mover works in unraid?

I'm currently viewing this script and I have checked out your fork for the mover tuning plugin, but that was difficult for me to follow at this point.

Okay so I think I'm now getting a good grasp on understanding the logic of the Mover Tuning Plugin. I spent a good chunk of time learning how to read PHP and BASH and have just been following the trail of files/code on your github.

 

The only thing left for me to read and understand is the loopcustomFIlelist() and loopArrayFilelist() functions in age_mover, which I will read tomorrow. Despite this, I think I have a good idea of how to approach implementing mover tunning functionality per share. It will be a lot of work especially for me who has never done this before, but I'm excited to give it a crack. I will create a fork of yours and work in that.

 

The only thing I could not follow was IF mover.old is run (by manually pressing the default "move now" button) it sends a list of all the files on the pool to "/usr/local/bin/move" which has code in it I was not able to read or follow. Seemed like it was partially encrypted or something lol.

Just as an update for anyone who might stumble across this thread, the changes to be able to change mover settings for individual shares is now officially implemented in the Mover Tuning Plugin. I've marked the first response to check out the Mover Tuning Plugin as the correct solution because well...it's now the correct solution!