6 hours ago, foamy said:

I'm not sure if this is a bug, or just expected behavior.

Reconstruct write should ideally only be enabled if there is content to move. I was scratching my head as to why my drives were spinning up unexpectedly, only to find the correlation in turbo write enabling being tied to the cron schedule of the plugin. I have a 3TB cache, and don't fill it quickly, so the unexpected spin-ups are just wasted electricity for me.

Automover session finished - 2025-11-08 08:00:01
Duration: 0s
Usage below threshold — nothing to do
cache usage: 15% Threshold:50% Stop Threshold:0%
Enabled reconstructive write mode (turbo write)
Automover session started - 2025-11-08 08:00:01

EDIT: Adding some clarity. My observation is this:

1. The plugin enables turbo write before checking if it's actually going to move anything. This should move to after the check

2. It doesn't revert the turbo write setting back to whatever it previously was.

In my case, My array is broken out into 3 user shares across 7 drives. I expect 3 of those 7 to be spun down nearly all the time. 1 of the 7 is specific to time machine backups, so it's spun up when backups are occurring/most of the time, and this is how I spotted that turbo writes were still going even when the automover plugin wasn't doing anything.

update is pushed, also made the change for stop/start containers so now they will only stop/start if files are going to be moved. did the same for the qbittorrent pause and resume

Edited November 8, 2025Nov 8 by jcofer555

On 11/8/2025 at 3:56 PM, jcofer555 said:

update is pushed, also made the change for stop/start containers so now they will only stop/start if files are going to be moved. did the same for the qbittorrent pause and resume

Thx, I think we have a new bug.

It seems to be ignoring the Threshold % setting, and just moving everything on every run. I have mine set at 75%, and the most recent run (after today's updated plugin) moved 2 files totaling less than 10GB of my 3TB cache. It no longer emits the percentage comparison into the log, so I think it's skipping the check. I have mine set at 75% and 0%, for the respective settings for threshold and stop threshold.

Automover session finished - 2025-11-12 00:02:45
Duration: 2m 44s
Completed jdupes step for media
No duplicates found.
Jdupes processing share media
Using existing jdupes database: /mnt/user/appdata/jdupes_hash_database.db
Cleanup of empty folders/datasets finished
Finished move process
Finished qbittorrent resume of torrents
Starting qbittorrent resume of torrents
Skipped 1 in-use file(s)
Finished move of 2 file(s) for share: media
Starting move of 2 file(s) for share: media
Finished qbittorrent pause of torrents
Starting qbittorrent pause of torrents
Finished move of 0 file(s) for share: download
Starting move of 1 file(s) for share: download
Starting move process

BTW, if you'd prefer these as GitHub issues, I can do that. One monolithic forum thread isn't a great medium for this type of thing. :)

Edited November 12, 2025Nov 12 by foamy

1 hour ago, foamy said:

Thx, I think we have a new bug.

It seems to be ignoring the Threshold % setting, and just moving everything on every run. I have mine set at 75%, and the most recent run (after today's updated plugin) moved 2 files totaling less than 10GB of my 3TB cache. It no longer emits the percentage comparison into the log, so I think it's skipping the check. I have mine set at 75% and 0%, for the respective settings for threshold and stop threshold.

Automover session finished - 2025-11-12 00:02:45
Duration: 2m 44s
Completed jdupes step for media
No duplicates found.
Jdupes processing share media
Using existing jdupes database: /mnt/user/appdata/jdupes_hash_database.db
Cleanup of empty folders/datasets finished
Finished move process
Finished qbittorrent resume of torrents
Starting qbittorrent resume of torrents
Skipped 1 in-use file(s)
Finished move of 2 file(s) for share: media
Starting move of 2 file(s) for share: media
Finished qbittorrent pause of torrents
Starting qbittorrent pause of torrents
Finished move of 0 file(s) for share: download
Starting move of 1 file(s) for share: download
Starting move process

BTW, if you'd prefer these as GitHub issues, I can do that. One monolithic forum thread isn't a great medium for this type of thing. :)

here is preferred for now
i see the issue and a fix has been released

26 minutes ago, jcofer555 said:

here is preferred for now
i see the issue and a fix has been released

Thank you. Logs cleared, will check it in the AM.

Much better :)

Automover session finished - 2025-11-12 06:00:01
Duration: 0s
Usage below threshold — nothing to do
cache usage:  1% Threshold:75% Stop Threshold:0%
Automover session started - 2025-11-12 06:00:01
------------------------------------------------

Edited November 12, 2025Nov 12 by foamy

love the plugin, would it be possible to stop all container instead of just specific ones?

(or to run a script before and after?)

50 minutes ago, leftHanded said:

love the plugin, would it be possible to stop all container instead of just specific ones?

(or to run a script before and after?)

stop all i can definitely do, the script one i'll have to look into further

On 12/7/2025 at 6:49 PM, leftHanded said:

love the plugin, would it be possible to stop all container instead of just specific ones?

(or to run a script before and after?)

got both added for you, ty for the suggestions

On 11/8/2025 at 3:56 PM, jcofer555 said:

update is pushed, also made the change for stop/start containers so now they will only stop/start if files are going to be moved. did the same for the qbittorrent pause and resume

I seem to be having trouble with qbittorrent pause and resume. It doesn't follow the rules as to which torrents to pause (ie. downloading, completed, etc.). It just seems to a handful of torrents and then doesn't resume them when it is done. The log claims it resumed, but when I log into qBitttorrent there are always 3 or 4 stopped.

1 hour ago, theimmortal said:

I seem to be having trouble with qbittorrent pause and resume. It doesn't follow the rules as to which torrents to pause (ie. downloading, completed, etc.). It just seems to a handful of torrents and then doesn't resume them when it is done. The log claims it resumed, but when I log into qBitttorrent there are always 3 or 4 stopped.

my last nights stop and resume seemed to work but i'll check again later today when i do some more. for you when it happens you can check the file /tmp/automover/automover_qbittorrent_paused.txt to make sure it's listed the torrents there which would confirm which were paused by the system and which the resume works off of when resuming. that file gets cleared on each move so it only keeps the pauses for each run it does so you gotta check it before the next run of automover happens.

8 hours ago, theimmortal said:

I seem to be having trouble with qbittorrent pause and resume. It doesn't follow the rules as to which torrents to pause (ie. downloading, completed, etc.). It just seems to a handful of torrents and then doesn't resume them when it is done. The log claims it resumed, but when I log into qBitttorrent there are always 3 or 4 stopped.

tonights went fine for me as well, i did just push an update so the pauses and resumes go to seperate log files so you can check those to see what it's saying

8 hours ago, jcofer555 said:

tonights went fine for me as well, i did just push an update so the pauses and resumes go to seperate log files so you can check those to see what it's saying

So, if I set it to only pause Downloads it works perfectly. When I have it set to active is when it doesn't seem to go as cleanly. It is likely I just need to continue to tweak my settings to get the desired results. Also, can you explain how the stop threshold is intended to work? I have mine set at 20%, but Automover never gets my cache drive that low. It generally moves about 15% (I have a 1TB cache drive) and finishes. So, for example, my threshold is at 70% and my stop threshold at 20%, Automover runs as expected sees the cache drive at 78% and triggers a move, but then when the move ends I will be at like 63%. My assumption is, since it skips in-use files, that since I have the qbittorrent set to downloads, that it is preventing some of my seeds to work correctly? Would just having it pause all torrents be a better option if my goal is to clear the majority of my cache drive during each run? I would rather a few large move operations rather than a series of smaller moves.

Also, I was wondering if you could add a switch to set jdupes to run with the -TT option (with an obvious warning so people understand the risk).

7 hours ago, theimmortal said:

So, if I set it to only pause Downloads it works perfectly. When I have it set to active is when it doesn't seem to go as cleanly. It is likely I just need to continue to tweak my settings to get the desired results. Also, can you explain how the stop threshold is intended to work? I have mine set at 20%, but Automover never gets my cache drive that low. It generally moves about 15% (I have a 1TB cache drive) and finishes. So, for example, my threshold is at 70% and my stop threshold at 20%, Automover runs as expected sees the cache drive at 78% and triggers a move, but then when the move ends I will be at like 63%. My assumption is, since it skips in-use files, that since I have the qbittorrent set to downloads, that it is preventing some of my seeds to work correctly? Would just having it pause all torrents be a better option if my goal is to clear the majority of my cache drive during each run? I would rather a few large move operations rather than a series of smaller moves.

Also, I was wondering if you could add a switch to set jdupes to run with the -TT option (with an obvious warning so people understand the risk).

the qbit script does pausing and resuming in one function. most people use the default status type of "completed" and then you set the days from and days to to whatever you want. this will pause any torrent that is completed and is withing those days so if a torrent is 3 days old and you have days from set to 0 and days to set to 2 than that 3 day old torrent won't be touched because it doesn't fall within.

stop threshold means if while moving the pool gets to that % the moving will stop, if you aren't reaching that low like you say then it would be because of ineligible files be it they are in use, set to exclusions, or filtered by a filter you have enabled or you have shares not set to move off of the pool. you can manually browse your pool and see what files are on it and if they are a bunch of torrent files from qbit and you want one big push of them off to the array before then using the qbit script to handle things from then yea you could just stop all torrents in qbit and use the move now button in automover to bypass all filters and exclusions you may have set so that it'll move everything it can that's not in use or set not to move from a shares settings.

i don't plan to add switches to jdupes i'm sorry but you can edit /usr/local/emhttp/plugins/automover/helpers/automover.sh and edit the line below to add your flags. keep in mind this would reset each unraid reboot

/usr/bin/jdupes -rLX onlyext:mp4,mkv,avi -y "$HASH_DB" "$SHARE_PATH" 2>&1 \

On 10/2/2025 at 11:18 AM, jcofer555 said:

@drmetro and @Johann the reporting of 1% on your pools has been fixed. it was zfs related, thanks drmetro for mentioning zfs and thanks @Rysz for further helping to determine where the issue was to be fixed

It looks to me like the stop threshold check still reports 1% for zfs pools.
It starts moving due usage of 96%, but then immediately stops due a usage of 1%:

Session finished - 2026-01-17 01:34:45
Duration: 4m 44s
No files moved — skipping jdupes step
Finished move process
Skipped 5 in-use file(s)
Finished move of 0 file(s) for share: data
Move stopped — pool usage reached stop threshold:   1% (<= 50%)
Starting move of 1149 file(s) for share: data
Enabled reconstructive write mode (turbo write)
Skipping appdata (array → pool moves not allowed)
Starting move process
cache_nvme usage:96% Threshold:80% Stop Threshold:50%
Session started - 2026-01-17 01:30:01

1 hour ago, Tore Hammervoll said:

It looks to me like the stop threshold check still reports 1% for zfs pools.
It starts moving due usage of 96%, but then immediately stops due a usage of 1%:

Session finished - 2026-01-17 01:34:45
Duration: 4m 44s
No files moved — skipping jdupes step
Finished move process
Skipped 5 in-use file(s)
Finished move of 0 file(s) for share: data
Move stopped — pool usage reached stop threshold:   1% (<= 50%)
Starting move of 1149 file(s) for share: data
Enabled reconstructive write mode (turbo write)
Skipping appdata (array → pool moves not allowed)
Starting move process
cache_nvme usage:96% Threshold:80% Stop Threshold:50%
Session started - 2026-01-17 01:30:01

Thanks for the report, ill have a look here soon

2 hours ago, Tore Hammervoll said:

It looks to me like the stop threshold check still reports 1% for zfs pools.
It starts moving due usage of 96%, but then immediately stops due a usage of 1%:

Session finished - 2026-01-17 01:34:45
Duration: 4m 44s
No files moved — skipping jdupes step
Finished move process
Skipped 5 in-use file(s)
Finished move of 0 file(s) for share: data
Move stopped — pool usage reached stop threshold:   1% (<= 50%)
Starting move of 1149 file(s) for share: data
Enabled reconstructive write mode (turbo write)
Skipping appdata (array → pool moves not allowed)
Starting move process
cache_nvme usage:96% Threshold:80% Stop Threshold:50%
Session started - 2026-01-17 01:30:01

how is your pool setup? i just tested on my zfs mirror and it's working properly

10 hours ago, jcofer555 said:

how is your pool setup? i just tested on my zfs mirror and it's working properly

I am seeing the same issue. I just started using Automover and thought maybe my settings were wrong, but then I came here and noticed I have the same issue as @Tore Hammervoll . I am running a single NVMe stick formatted as zfs (not mirrored).

17 hours ago, jcofer555 said:

how is your pool setup? i just tested on my zfs mirror and it's working properly

Not sure what sort of details you're looking for, but I have 5 xfs formatted array disks and a single parity.

Looking at the source code, I think this is the offending line: https://github.com/jcofer555/automover/blob/99b4d474624474e28378b818d83c2fb2d2758a0b/src/usr/local/emhttp/plugins/automover/helpers/automover.sh#L984

It doesn't have the same alternate logic for zfs as the other usages of `df`, and it fits with the log message where I see it reports 1% usage.

23 minutes ago, Tore Hammervoll said:

Not sure what sort of details you're looking for, but I have 5 xfs formatted array disks and a single parity.

Looking at the source code, I think this is the offending line: https://github.com/jcofer555/automover/blob/99b4d474624474e28378b818d83c2fb2d2758a0b/src/usr/local/emhttp/plugins/automover/helpers/automover.sh#L984

It doesn't have the same alternate logic for zfs as the other usages of `df`, and it fits with the log message where I see it reports 1% usage.

the fix has been released as v2026.01.17.01 @Stardog and @Tore Hammervoll

hi. just checking. why does the move now button doesnt seem to do anything?

47 minutes ago, i1mran92 said:

hi. just checking. why does the move now button doesnt seem to do anything?

Its not finding any files to move. Is there a share on that pool that is configured with secondary storage and mover direction pool -> pool or pool ->array?

2 minutes ago, jcofer555 said:

Its not finding any files to move. Is there a share on that pool that is configured with secondary storage and mover direction pool -> pool or pool ->array?

i have a separate dedicate cache driver. it is setup currently as per screenshot.

3 minutes ago, i1mran92 said:

i have a separate dedicate cache driver. it is setup currently as per screenshot.

And there's files in the data share that are on that pool? Can verify by clicking compute for the share and seeing what disks comes up

2 minutes ago, jcofer555 said:

And there's files in the data share that are on that pool? Can verify by clicking compute for the share and seeing what disks comes up

i just tried setting the mover to run in 5mins, and it did moved the files. just that the move now button doesnt seem to do anything.
also, not sure why but it left some empty folder as well.

4 minutes ago, i1mran92 said:

i just tried setting the mover to run in 5mins, and it did moved the files. just that the move now button doesnt seem to do anything.
also, not sure why but it left some empty folder as well.

Odd as move now should disable any filters preventing files from moving so thats weird it didn't do it

For cleanup of empty folders parts. Was it folders not involved with the move of files? Iirc I have it so it removes empty folders that had a file moved

1 minute ago, jcofer555 said:

Odd as move now should disable any filters preventing files from moving so thats weird it didn't do it

For cleanup of empty folders parts. Was it folders not involved with the move of files? Iirc I have it so it removes empty folders that had a file moved

first tested move now from the plugin didnt work. then changed settings to run every 5mins, that did it. but left that empty folder.
then i used unraid default mover, and that cleans everything up. so i'm also at kinda confuse.

if u have any suggestion of a test i can do it as well.