On 4/4/2026 at 1:06 AM, ados said:

Any thoughts on this, make sense? Good idea?

it's a good idea yes, i've tried to implement it a few times by looking at how mover tuning does it as that plugin does it well for age based moving options but my attempts to add it to automover have been unsuccessful so far but it's for sure something i'd love to accomplish

1 hour ago, jcofer555 said:

only if you wanted automover when moving files to have more or less i/o priority from the system than normal.

What does the scale mean? Is Normal on the left of the scale, and Idle on the right side of the scale, that means Best Efforts is somewhere between Normal and Idle? Why are there so many Best Efforts?

I/O Priority:

Normal

Best-effort 0

Best-effort 1

Best-effort 2

Best-effort 3

Best-effort 4

Best-effort 5

Best-effort 6

Best-effort 7

Idle

...I'm trying to figure out which is best to use (ideally):

1) Prioritize productivity. This is mostly read from SSD cache pool, and/or reading Plex/Jellyfin media from array for when watching a movie/show.

2) De-prioritize Dynamix Integrity check.

3) De-prioritize Parity check.

4) De-prioritize torrent client reads from array/cache. But I also have a separate pool for torrent writes which I want to have high/normal priority.

Basically, I want cache moved to array as quickly/soon as possible, unless I'm the user or I need torrents moved from torrent pool to the cache...

...and since the Integrity check started, the mover is taking forever, and I assume there's competition for resources. But I won't know for sure until I see the start time and transfer rate posted to the log at the end of the move. It's also possible there's a bug. Automover is showing the mover is active, but I haven't seen the log update for a long time.

Edited April 5Apr 5 by Jaybau

33 minutes ago, Jaybau said:

What does the scale mean? Is Normal on the left of the scale, and Idle on the right side of the scale, that means Best Efforts is somewhere between Normal and Idle? Why are there so many Best Efforts?

I/O Priority:

Normal

Best-effort 0

Best-effort 1

Best-effort 2

Best-effort 3

Best-effort 4

Best-effort 5

Best-effort 6

Best-effort 7

Idle

...I'm trying to figure out which is best to use (ideally):

1) Prioritize productivity. This is mostly read from SSD cache pool, and/or reading Plex/Jellyfin media from array for when watching a movie/show.

2) De-prioritize Dynamix Integrity check.

3) De-prioritize Parity check.

4) De-prioritize torrent client reads from array/cache. But I also have a separate pool for torrent writes which I want to have high/normal priority.

Basically, I want cache moved to array as quickly/soon as possible, unless I'm the user or I need torrents moved from torrent pool to the cache...

...and since the Integrity check started, the mover is taking forever, and I assume there's competition for resources. But I won't know for sure until I see the start time and transfer rate posted to the log at the end of the move. It's also possible there's a bug. Automover is showing the mover is active, but I haven't seen the log update for a long time.

normal is roughly best-effort 3, so if you change from normal to something else if you go above 4 it means it will take more than normal system i/o to be dedicated to automovers move and less than 3 means it'll take less than normal and then idle is the highest

11 hours ago, jcofer555 said:

should be fixed in latest update

it's 100% a personal preference and for me i prefer it on top, you could edit the code with a userscript on array start for the schedule so that those tooltips show below not above if you'd like as an option to get it how you want

oh no sorry, i didnt meant it that way. i just meant the description of it. it says "settings shown above" but isnt all the settings are below that description. haha.

also, regarding jdupes from my same comment, do you have any info about that? thank you

this
"also, another thing i notice, is that if i dont enable jdupes, qbittorrent will report alot of noHL for recent torrent that just been downloaded and moved by automover.
this doesnt happen when using the built in unraid mover. i always stop qbit, run mover, and start back qbit after mover ends.
is there anything misconfigure?"

does jdupes something usually we need to enable? it also takes significantly longer for the mover process to finish.

thanks again for the latest update about cleaning the empty folders. will test it out.

Edited April 6Apr 6 by i1mran92

19 minutes ago, i1mran92 said:

oh no sorry, i didnt meant it that way. i just meant the description of it. it says "settings shown above" but isnt all the settings are below that description. haha.

also, regarding jdupes from my same comment, do you have any info about that? thank you

this
"also, another thing i notice, is that if i dont enable jdupes, qbittorrent will report alot of noHL for recent torrent that just been downloaded and moved by automover.
this doesnt happen when using the built in unraid mover. i always stop qbit, run mover, and start back qbit after mover ends.
is there anything misconfigure?"

does jdupes something usually we need to enable? it also takes significantly longer for the mover process to finish.

thanks again for the latest update about cleaning the empty folders. will test it out.

oh lmao i didn't catch that, that's kinda funny, i'll have to adjust that now cause it'll bug me lol. as far as qbit show noHL after automover moves i'm not sure why it'd do that because automover uses rsync with the -H flag with is for hardlinking. my experience has been they are fine and i've not heard of others having the issue yet. i'll dig in and ask some of my testers and see if anything comes up but i'm not sure on that issue

great plugin! intuitive and easy to setup. per pool is a nice way to go! wish it had hours for file age instead of days, but pools is a nice way to set these up!

development has ended on my plugins for the time being