Automatic Torrent Management mode does not relocate torrent in case of common files #7276

New issue

Closed

opened 2026-02-21 18:52:45 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 18:52:45 -05:00

Owner

Originally created by @slrslr on GitHub (May 12, 2018).

qBittorrent version and Operating System

4.1.0, Windows 10 64b

What is the problem

In qbt i typed a phrase to filter out torrents matching it. Result was 5 torrents, i highlighted these all, right click and selected new category (it was child of a current category) in aim to relocate these torrents.

then i see only 2 out of 5 changed its Save Path.

The ones that succeeded was in "Automatic Torrent Management" mode. So this is good.

From remaining three, two was in manual mode. So why Automatic mode torrent was not relocated? I think because it has common payload path with remaining two that was in manual mode. I will illustrate the failed (not relocated) torrents details:

2 /ParentDir/PayloadFolderMovie/PayloadfileBestMovie.mp4 | automatic | failed
3 /ParentDir/Movie/PayloadfileBestMovie.mp4 | manual | failed
4 /ParentDir/Movie/PayloadfileBestMovie.mp4 | manual | failed

The torrent number "2" has folder and child file in its payload, but torrents 3 and 4 do not have any folder in payload, so i had to disable Automatic Torrent Management for these two and manually find folder created by torrent 2 - /Parent/PayloadFolderMovie/ and set it as a Save Path for the remaining two torrents (which are in Manual mode).

This way i am causing hidden issue in case i need to relocate torrents later. (relocate will hiddenly fail)

I am glad qbt not relocated the torrent "2" because it would break other two manual mode torrents i think. It do not relocate it even if i select relocation only for this one particular torrent that is in automatic mode (not all three torrents at time). But yet i think this create confusion/mess. Is there any way this can be improved?

This reminds me an idea #6520 where once i make some change in torrents payload or save path, the qbt will first search rest of the torrents to find common paths and same file sizes and TELL me that it found some other torrents that seems to be the same and ASK if i want to rename its payload paths/filenames/relocate them too. And update Save Path's or payload paths or payload file names so it match. The issue #439 seems similar too. Maybe this feature is too difficult to create, do not know, but still think it is important to somehow handle case when multiple torrents share same file/s having dfifferent payload structures.

Originally created by @slrslr on GitHub (May 12, 2018). ### qBittorrent version and Operating System 4.1.0, Windows 10 64b ### What is the problem In qbt i typed a phrase to filter out torrents matching it. Result was 5 torrents, i highlighted these all, right click and selected new category (it was child of a current category) in aim to relocate these torrents. then i see only 2 out of 5 changed its Save Path. The ones that succeeded was in "Automatic Torrent Management" mode. So this is good. From remaining three, two was in manual mode. So why Automatic mode torrent was not relocated? I think because it has common payload path with remaining two that was in manual mode. I will illustrate the failed (not relocated) torrents details: 2 /ParentDir/**PayloadFolder**Movie/PayloadfileBestMovie.mp4 | automatic | failed 3 /ParentDir/Movie/PayloadfileBestMovie.mp4 | manual | failed 4 /ParentDir/Movie/PayloadfileBestMovie.mp4 | manual | failed The torrent number "2" has folder and child file in its payload, but torrents 3 and 4 do not have any folder in payload, so i had to disable Automatic Torrent Management for these two and manually find folder created by torrent 2 - /Parent/PayloadFolderMovie/ and set it as a Save Path for the remaining two torrents (which are in Manual mode). This way i am causing hidden issue in case i need to relocate torrents later. (relocate will hiddenly fail) I am glad qbt not relocated the torrent "2" because it would break other two manual mode torrents i think. It do not relocate it even if i select relocation only for this one particular torrent that is in automatic mode (not all three torrents at time). But yet i think this create confusion/mess. Is there any way this can be improved? This reminds me an idea #6520 where once i make some change in torrents payload or save path, the qbt will first search rest of the torrents to find common paths and same file sizes and TELL me that it found some other torrents that seems to be the same and ASK if i want to rename its payload paths/filenames/relocate them too. And update Save Path's or payload paths or payload file names so it match. The issue #439 seems similar too. Maybe this feature is too difficult to create, do not know, but still think it is important to somehow handle case when multiple torrents share same file/s having dfifferent payload structures.

deekerman

2026-02-21 18:52:45 -05:00

closed this issue
added the
OS: Windows
label

deekerman commented

2026-02-21 18:52:50 -05:00

Author

Owner

@slrslr commented on GitHub (Sep 10, 2019):

Maybe qbt not relocated it, because after qbt moved first torrent and its data, it could not find the data for other torrent to move, so it skipped.

Maybe qbt should be instructed to check destination folder and if it contains data already, it should proceed changing savepath.

Currently i have to monitor save paths of the torrents i am relocating and making sure to manually disable and enable "Automatic torrent management mode" which will change savepath. (?)

@slrslr commented on GitHub (Sep 10, 2019): Maybe qbt not relocated it, because after qbt moved first torrent and its data, it could not find the data for other torrent to move, so it skipped. Maybe qbt should be instructed to check destination folder and if it contains data already, it should proceed changing savepath. Currently i have to monitor save paths of the torrents i am relocating and making sure to manually disable and enable "Automatic torrent management mode" which will change savepath. (?)

deekerman commented

2026-02-21 18:52:50 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Apr 27, 2021):

4.1 series of qBittorrent are no longer supported

If you experience this issue with qBittorrent 4.3.4.1 or later, please feel free to open a "New Issue"

@xavier2k6 commented on GitHub (Apr 27, 2021): 4.1 series of qBittorrent are no longer supported If you experience this issue with qBittorrent **4.3.4.1** or later, please feel free to open a "New Issue"