[Wishlist] Status indicators for file moving operations #5263

New issue

Closed

opened 2026-02-21 17:45:24 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 17:45:24 -05:00

Owner

Originally created by @ghost on GitHub (Feb 25, 2017).

I download torrents to SSD in an "incomplete" folder, and then when my downloads are finished, they get moved to my NAS. The transfer can take a considerable amount of time for 50+GB torrents, but there is no indication of what the progress is within qBittorrent.

There is another scenario where this would be helpful. If you have a bunch of active torrents, and go into qBittorrent's options and change where incomplete files are stored, everything that is currently active stalls out while all of the incomplete torrent content gets moved over to the new location (this process is actually very slick.. kudos). This can take a very long time if there's a lot of active torrents, and it would be really nice to get an idea of how long it will take.

I would suggest adding another status category "Moving", with a progress bar, alongside downloading/seeding/paused/etc

Thanks

Originally created by @ghost on GitHub (Feb 25, 2017). I download torrents to SSD in an "incomplete" folder, and then when my downloads are finished, they get moved to my NAS. The transfer can take a considerable amount of time for 50+GB torrents, but there is no indication of what the progress is within qBittorrent. There is another scenario where this would be helpful. If you have a bunch of active torrents, and go into qBittorrent's options and change where incomplete files are stored, everything that is currently active stalls out while all of the incomplete torrent content gets moved over to the new location (this process is actually very slick.. kudos). This can take a very long time if there's a lot of active torrents, and it would be really nice to get an idea of how long it will take. I would suggest adding another status category "Moving", with a progress bar, alongside downloading/seeding/paused/etc Thanks

deekerman

2026-02-21 17:45:24 -05:00

closed this issue
added the
Duplicate
label

deekerman commented

2026-02-21 17:45:31 -05:00

Author

Owner

@coolio2013 commented on GitHub (Feb 26, 2017):

+1
-an user initiated closing of qbt must be considered as well, while a move is active. A crash while moving is really bad (storing source and target and completion in .fastresume to continue would be awesome)
-since quite a while, only the entire payload (say, a complete folder) is moved, not file by file any more
-finally: moves should be put into the LOG, with source and target and when it is finished

But I assume, all is probably a matter of libtorrent, except logging.

Thanks devs!

@coolio2013 commented on GitHub (Feb 26, 2017): +1 -an user initiated closing of qbt must be considered as well, while a move is active. A crash while moving is really bad (storing source and target and completion in .fastresume to continue would be awesome) -since quite a while, only the entire payload (say, a complete folder) is moved, not file by file any more -finally: moves should be put into the LOG, with source and target and when it is finished But I assume, all is probably a matter of libtorrent, except logging. Thanks devs!

deekerman commented

2026-02-21 17:45:31 -05:00

Author

Owner

@thalieht commented on GitHub (May 3, 2017):

#508 duplicate

@thalieht commented on GitHub (May 3, 2017): #508 duplicate

deekerman commented

2026-02-21 17:45:31 -05:00

Author

Owner

@thalieht commented on GitHub (Jul 25, 2018):