search

qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
27.45k stars 3.9k forks source link

Improvements when moving a huge torrent #508

Open sledgehammer999 opened 11 years ago

sledgehammer999 commented 11 years ago

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

iheartcsharp commented 2 years ago

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.

ericrosenberg1 commented 1 year ago

Would love to see this implemented

bagobones commented 1 year ago

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.

SeanVella commented 6 months ago

Bump this! We need it!

alexx-ftw commented 6 months ago

Bump. This is a much needed QoL improvement

nathan815 commented 6 months ago

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.

phanirithvij commented 6 months ago

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

mirddes commented 3 months ago

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