qBittorrent icon indicating copy to clipboard operation
qBittorrent copied to clipboard

Published 20 hours ago • verified publisher icon qbittorrent

Improvements when moving a huge torrent

Open sledgehammer999 opened this issue 12 years ago • 8 comments

Tracking upstream bug: https://code.google.com/p/libtorrent/issues/detail?id=444&start=100

If it is implement:

  1. We should report the move progress to user
  2. Shutdown libtorrent correctly during a move. Currently the torrent state is corrupted.

Edit: New upstream issue is at https://github.com/arvidn/libtorrent/issues/2923 and stalled due to a technical obstacle described in https://github.com/arvidn/libtorrent/issues/2923#issuecomment-397900182

sledgehammer999 avatar Mar 16 '13 11:03 sledgehammer999

Until this feature gets added to libtorrent, there are two simple workarounds.

  1. Since qBittorrent knows the torrent size, it can poll the new location every second and get the file size. Use the destination file size and divide by the torrent size. This would give you the progress. Not sure if this would work for all file systems so probably not the best option.
  2. qBittorrent can do a copy using the system I/O. Once the copy is finished, update the torrent to the new path. Once it's been accepted, delete the original location. Basically a copy-on-write functionality.

Any thoughts on this? I think #2 would be more robust and easier.

iheartcsharp avatar Oct 25 '21 16:10 iheartcsharp

Would love to see this implemented

ericrosenberg1 avatar Oct 28 '22 21:10 ericrosenberg1

I download to a temp location them MOVE to a much slower network drive as rapid IO during download works much better on a fast local drive and a long continuous transfer tends to work well over network.

However moves are SLOW, VERY SLOW and the lack of progress is quite concerning on large transfers.

I would love to see a move progress bar of some kind or possibly a different move implementation as there are some other tickets that note using OS native file transfers can lead to much faster and reliable transfers in some cases.

bagobones avatar Aug 14 '23 04:08 bagobones

Bump this! We need it!

SeanVella avatar Mar 27 '24 11:03 SeanVella

Bump. This is a much needed QoL improvement

alexx-ftw avatar Mar 28 '24 16:03 alexx-ftw

This would be great. It's been painfully slow to move files between docker volume mounts (on same physical drive), but showing the progress would make it a lot better.

nathan815 avatar Apr 03 '24 05:04 nathan815

Please upvote the top post, more bump comments add nothing.

The new upstream issue is at https://github.com/arvidn/libtorrent/issues/2923 but it was closed by stale bot

phanirithvij avatar Apr 08 '24 05:04 phanirithvij

enabling implementation of some indication of file movement progression in downstream clients would be greatly appreciated.

mirddes avatar Jun 16 '24 11:06 mirddes

+1

littlefisher666 avatar Nov 27 '24 05:11 littlefisher666

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future! Here are some options available to you:

  1. Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.

  2. Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket. (new/existing contributors/developers are always welcome)

DO:

  • Provide constructive feedback.
  • Display how other projects implemented same/similar etc.

DO NOT:

  • Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). (These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

xavier2k6 avatar May 23 '25 18:05 xavier2k6