TRaSH

Okay, I think I've figured out the issue I was having, and this could also be the issue for others who experience problems where it appears the mover doesn't work. I couldn't see any single file in my cache that was taking up space, And my 4 TB cache was 90% full. So, something is reserving the space, and it won't be released until you quit qBittorrent. In qBittorrent, disable the "Pre-allocate disk space for all files" option under Settings -> Downloads. I've been testing this option for over 8 days, and it appears to have finally cleared my cache drive.

I might have an idea to what it could be related, but i want to test it first before making assumptions

I used ncdu, everything was empty in my case But even with ls -alh and what you mentioned it was empty

I use a script to pause and resume the torrents that are x days old. But the weirdest part was that i couldn't see any single file on my cache what was taking up the space. And my 4 TB cache was for 90% full So something is reserving the space and it won't be released before you quit Qbt

Okay i did some own research, after i disabled the option that the mover button should ignore the settings, i still didn't move all the files, so i was wondering why my cache said it was full when the actual size on the cache used was much smaller. When i decided to stop my Qbt instances for a few minutes it magically released all the space. So perhaps something others want to test

Okay, I've set it to get triggered at 75% and clear till 25% but still nothing gets moved. I wonder if i should just disable the follow rules and just force move everything and then see what will happen

1. I changed it to 50/20% 2. Shouldn't this option say: screw it, I'm moving it anyway?

@Masterwishx could you also look at this one why it's failing?

For some reason, the mover isn't clearing my /data share anymore, and my cache drive is at 95% And IIRC, with the following settings, it should clear my cache drive. So I'm wondering why it's not moving the files of the cache drive. Provided also my mover tuning debug ca.mover.tuning-debug-20250908-0131.zip

The same happened here after I upgraded, just need to figure out how to downgrade to a working version.

I'm testing something new with this plugin and trying to run a script after the mover tuning started but somehow i get a error that it can't find the script. Fastdrive = another nvme drive i'm using ``` Sep 1 19:46:58 root: Starting Mover Sep 1 19:46:58 root: Forcing turbo write on Sep 1 19:46:58 kernel: mdcmd (92): set md_write_method 1 Sep 1 19:46:58 kernel: Sep 1 19:46:58 root: ionice -c 2 -n 7 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start 10 0 0 '' '' '' "/mnt/fastdrive/userScripts/userScripts/mover-after.sh" yes 90 '' '' 30 Sep 1 19:46:58 root: Log Level: 1 Sep 1 19:46:58 root: mover: started Sep 1 19:46:58 root: mover: finished Sep 1 19:46:58 root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 849: /mnt/fastdrive/userScripts/userScripts/mover-after.sh: cannot execute: required file not found Sep 1 19:46:58 root: Restoring original turbo write mode ``` Solved: CRLF vs LF Left it here for others if they run in to the same issue

In my current setup i use bonding (Mode 4 (802.3ad)), main reason was because when I'm doing heavy traffic up/download, i got issues during plex playback because my nic was fully saturated. With these changes i have the feeling i will go back to the same issues before i decided to bond them.

I recently upgraded and switched and had exactly the same issue. kinda annoying that the so called not supported nerd tools has a working version and the replacement has a borked version if you still have the old nerdtools installed you can install a version that still works

Thnx for this one, wish there was something like this for WD nvme's

This should be added in bold text to the changelog including instructions how to load the necessary packages !!!