starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Failure to move completed torrents #16090

New issue

Open

opened 2026-02-22 02:47:25 -05:00 by deekerman · 14 comments

deekerman commented

2026-02-22 02:47:25 -05:00

Owner

Originally created by @greenfedora on GitHub (Sep 27, 2024).

qBittorrent & operating system versions

qBittorrent v4.6.3 (64-bit)
Ubuntu 24.04.1 LTS
Qt: 6.4.2
Libtorrent: 2.0.10.0
Boost: 1.83.0
OpenSSL: 3.0.13
zlib: 1.3

What is the problem?

Fails to move torrents on completion. The first one moved correctly, there are now 478 torrents with status Moving but none have moved since yesterday.

Steps to reproduce

Moved to using a new USB drive.
Uninstalled qbittorrent
Deleted settings
set "Default Path" and "use another path for incomplete torrents"
copied old downloads (partial and complete) to the incomplete downloads path
copied old torrent files to watched folder
Waited while files were checked
Noticed first file completed was moved and is now seeding
All files are now checked and 478 files of 562 have the status Moving.
turned off watched folder - no effect.

Additional context

All torrent directories are on a usb drive set up in fstab and auto mounted. All permissions are set to allow the qbittorrent user to have full control.

Log(s) & preferences file(s)

qBittorrent.conf.txt

Originally created by @greenfedora on GitHub (Sep 27, 2024). ### qBittorrent & operating system versions qBittorrent v4.6.3 (64-bit) Ubuntu 24.04.1 LTS Qt: 6.4.2 Libtorrent: 2.0.10.0 Boost: 1.83.0 OpenSSL: 3.0.13 zlib: 1.3 ### What is the problem? Fails to move torrents on completion. The first one moved correctly, there are now 478 torrents with status Moving but none have moved since yesterday. ### Steps to reproduce Moved to using a new USB drive. Uninstalled qbittorrent Deleted settings set "Default Path" and "use another path for incomplete torrents" copied old downloads (partial and complete) to the incomplete downloads path copied old torrent files to watched folder Waited while files were checked Noticed first file completed was moved and is now seeding All files are now checked and 478 files of 562 have the status Moving. turned off watched folder - no effect. ### Additional context All torrent directories are on a usb drive set up in fstab and auto mounted. All permissions are set to allow the qbittorrent user to have full control. ### Log(s) & preferences file(s) [qBittorrent.conf.txt](https://github.com/user-attachments/files/17171574/qBittorrent.conf.txt)

deekerman added the

Libtorrent

label

2026-02-22 02:47:25 -05:00

deekerman commented

2026-02-22 02:47:32 -05:00

Author

Owner

@greenfedora commented on GitHub (Sep 27, 2024):

The log file is snowed with "9/28/24 12:23 PM - Unexpected data detected. Torrent: XXX. Data: total_wanted=22456521 total_wanted_done=22462464."
I've put the offending torrents on hold. I will see if anything else turns up.

@greenfedora commented on GitHub (Sep 27, 2024): The log file is snowed with "9/28/24 12:23 PM - Unexpected data detected. Torrent: XXX. Data: total_wanted=22456521 total_wanted_done=22462464." I've put the offending torrents on hold. I will see if anything else turns up.

deekerman commented

2026-02-22 02:47:34 -05:00

Author

Owner

@qBittUser commented on GitHub (Sep 28, 2024):

Can you reproduce using latest stable official AppImage qBittorrent v4.6.7 with libtorrent 1.2.19+ from the download page?

@qBittUser commented on GitHub (Sep 28, 2024): Can you reproduce using latest stable official AppImage qBittorrent v4.6.7 with libtorrent 1.2.19+ from the [download](https://www.qbittorrent.org/download) page?

deekerman commented

2026-02-22 02:47:34 -05:00

Author

Owner

@greenfedora commented on GitHub (Sep 28, 2024):

I found I was using the unstable ppa (not sure why it isn't as up to date as the stable?). Switched to the Stable:
qbittorrent 4.6.7
Qt: 6.4.2
Libtorrent: 2.0.11.0
Boost: 1.83.0
OpenSSL: 3.0.13
zlib: 1.3

But are you suggesting using Libtorrent 1.2 rather than 2.0?

@greenfedora commented on GitHub (Sep 28, 2024): I found I was using the unstable ppa (not sure why it isn't as up to date as the stable?). Switched to the Stable: qbittorrent 4.6.7 Qt: 6.4.2 Libtorrent: 2.0.11.0 Boost: 1.83.0 OpenSSL: 3.0.13 zlib: 1.3 But are you suggesting using Libtorrent 1.2 rather than 2.0?

deekerman commented

2026-02-22 02:47:34 -05:00

Author

Owner

@qBittUser commented on GitHub (Sep 28, 2024):

@greenfedora

But are you suggesting using Libtorrent 1.2 rather than 2.0?

Both behave differently and have something good or bad.

If updating qBittorrent didn't help, then try with libtorrent 1.2+, it might work better with external drives. Afterwards I would update used dependencies to latest and try using AppImage instead of PPA.

If you try doing basic tests yourself, then others might not need to guess what is or isn't causing issues.

@qBittUser commented on GitHub (Sep 28, 2024): @greenfedora > But are you suggesting using Libtorrent 1.2 rather than 2.0? Both behave differently and have something good or bad. If updating qBittorrent didn't help, then try with libtorrent 1.2+, it might work better with external drives. Afterwards I would update used dependencies to latest and try using AppImage instead of PPA. If you try doing basic tests yourself, then others might not need to guess what is or isn't causing issues.

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@greenfedora commented on GitHub (Sep 28, 2024):

The Appimage with libtorrent 1.2+ works! That means it is libtorrent 2.0 that's the problem, right? I don't know how to get the ppa to use an earlier version of libtorrent so I'll just keep using the Appimage.

Are there other tests I can do to narrow down the bug? Keen to provide as much help to you guys as I can!

@greenfedora commented on GitHub (Sep 28, 2024): The Appimage with libtorrent 1.2+ works! That means it is libtorrent 2.0 that's the problem, right? I don't know how to get the ppa to use an earlier version of libtorrent so I'll just keep using the Appimage. Are there other tests I can do to narrow down the bug? Keen to provide as much help to you guys as I can!

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@greenfedora commented on GitHub (Oct 1, 2024):

Not sure it's related but the AppImage keeps closing down:
kerry@sprint:~/Downloads$ ./qbittorrent-4.6.7_x86_64.AppImage
Killed
Nothing in the logs, it just closes with no message.

I'm also getting the log filling up with these two file related errors:
10/1/24 5:26 PM - Unexpected data detected. Torrent: [XXXXX] Data: total_wanted=4686318 total_wanted_done=4702208.
And
10/1/24 5:27 PM - File error alert. Torrent: [XXXXX] File: ["/XXXXXX]. Reason: error: No such file or directory"

@greenfedora commented on GitHub (Oct 1, 2024): Not sure it's related but the AppImage keeps closing down: kerry@sprint:~/Downloads$ ./qbittorrent-4.6.7_x86_64.AppImage Killed Nothing in the logs, it just closes with no message. I'm also getting the log filling up with these two file related errors: 10/1/24 5:26 PM - Unexpected data detected. Torrent: [XXXXX] Data: total_wanted=4686318 total_wanted_done=4702208. And 10/1/24 5:27 PM - File error alert. Torrent: [XXXXX] File: ["/XXXXXX]. Reason: error: No such file or directory"

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@qBittUser commented on GitHub (Oct 1, 2024):

Try qBit v5.0.0 with libtorrent 1.2+ and force recheck torrents.

Currently there's only 1 more open and 1 closed issue that mention both the Unexpected data detected & total_wanted_done you saw in your log.

https://github.com/qbittorrent/qBittorrent/issues?q=Unexpected+data+detected+total_wanted_done

Maybe your internal drive and external USB drive can't handle the read and write load with your high settings.
Maybe drives have errors and needs replacement.
Maybe you have multiple torrents that share same folder and filenames.
Maybe torrents you have issues with have something in common, such as some files are unchecked from being downloaded or folder or filenames or your OS isn't fully compatible with external USB drives filesystem.

@qBittUser commented on GitHub (Oct 1, 2024): Try qBit v5.0.0 with libtorrent 1.2+ and force recheck torrents. Currently there's only 1 more open and 1 closed issue that mention both the `Unexpected data detected` & `total_wanted_done` you saw in your log. https://github.com/qbittorrent/qBittorrent/issues?q=Unexpected+data+detected+total_wanted_done Maybe your internal drive and external USB drive can't handle the read and write load with your high settings. Maybe drives have errors and needs replacement. Maybe you have multiple torrents that share same folder and filenames. Maybe torrents you have issues with have something in common, such as some files are unchecked from being downloaded or folder or filenames or your OS isn't fully compatible with external USB drives filesystem.

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@unregd commented on GitHub (Nov 30, 2024):

qBittorrent v5.0.2 (64-bit)
Windows 10 pro

Qt: 6.7.3
Libtorrent: 1.2.19.0
Boost: 1.86.0
OpenSSL: 3.4.0
zlib: 1.3.1

When I manually move a freshly downloaded torrent from x:\dir1 to x:\dir2 qB throws this error around a hundred times.:
2024-11-30 17:34 - Unexpected data detected. Torrent: xxxxxx. Data: total_wanted=1792291497 total_wanted_done=1792294912.

SATA HDD, NTFS, default 4K cluster size.
This error happens seemingly randomly, but it may be related to the load of the HDD, and may happened when other torrents were also donwloaded to it.
The qB cache is set to 16GiB, I have 64GiB RAM, OS cache is also enabled.
That error means (and the number matches) the sum of the size of the files on the disk is larger than the size defined in the .torrent file,
qB just freshly downloaded them, then tries to move them from foldar 'A' to folder 'B' on the same drive.
There are no matching torrents, folders or files, the torrent and files are unique.

@unregd commented on GitHub (Nov 30, 2024): qBittorrent v5.0.2 (64-bit) Windows 10 pro Qt: 6.7.3 Libtorrent: 1.2.19.0 Boost: 1.86.0 OpenSSL: 3.4.0 zlib: 1.3.1 When I manually move a freshly downloaded torrent from x:\dir1 to x:\dir2 qB throws this error around a hundred times.: 2024-11-30 17:34 - Unexpected data detected. Torrent: xxxxxx. Data: total_wanted=1792291497 total_wanted_done=1792294912. SATA HDD, NTFS, default 4K cluster size. This error happens seemingly randomly, but it may be related to the load of the HDD, and may happened when other torrents were also donwloaded to it. The qB cache is set to 16GiB, I have 64GiB RAM, OS cache is also enabled. That error means (and the number matches) the sum of the size of the files on the disk is larger than the size defined in the .torrent file, qB just freshly downloaded them, then tries to move them from foldar 'A' to folder 'B' on the same drive. There are no matching torrents, folders or files, the torrent and files are unique.

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@glassez commented on GitHub (Dec 1, 2024):

That error means (and the number matches) the sum of the size of the files on the disk is larger than the size defined in the .torrent file

In fact, it is assumed that libtorrent contains a bug in the logic of some counters, so I added this diagnostic message to try to find the conditions for its occurrence. If I'm right, then everything is fine with the files (their sizes match the ones from the torrent metadata), so if you force recheck torrent, it will show 100% progress without any errors.
@arvidn, ping.

@glassez commented on GitHub (Dec 1, 2024): > That error means (and the number matches) the sum of the size of the files on the disk is larger than the size defined in the .torrent file In fact, it is assumed that `libtorrent` contains a bug in the logic of some counters, so I added this diagnostic message to try to find the conditions for its occurrence. If I'm right, then everything is fine with the files (their sizes match the ones from the torrent metadata), so if you force recheck torrent, it will show 100% progress without any errors. @arvidn, ping.

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@unregd commented on GitHub (Dec 1, 2024):

That error means (and the number matches) the sum of the size of the files on the disk is larger than the size defined in the .torrent file

In fact, it is assumed that libtorrent contains a bug in the logic of some counters, so I added this diagnostic message to try to find the conditions for its occurrence. If I'm right, then everything is fine with the files (their sizes match the ones from the torrent metadata), so if you force recheck torrent, it will show 100% progress without any errors. @arvidn, ping.

Yup, I did not specify clearly, the problem is the error popping up a hundred times for no reason, not files getting corrupt or something like that. An annoyance.

@unregd commented on GitHub (Dec 1, 2024): > > That error means (and the number matches) the sum of the size of the files on the disk is larger than the size defined in the .torrent file > > In fact, it is assumed that `libtorrent` contains a bug in the logic of some counters, so I added this diagnostic message to try to find the conditions for its occurrence. If I'm right, then everything is fine with the files (their sizes match the ones from the torrent metadata), so if you force recheck torrent, it will show 100% progress without any errors. @arvidn, ping. Yup, I did not specify clearly, the problem is the error popping up a hundred times for no reason, not files getting corrupt or something like that. An annoyance.

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@arvidn commented on GitHub (Dec 1, 2024):

In fact, it is assumed that libtorrent contains a bug in the logic of some counters

What's the counter? And is "unexpected data detected", is that when files on disk are larger than they're supposed to be, according to the .torrent file?

@arvidn commented on GitHub (Dec 1, 2024): > In fact, it is assumed that libtorrent contains a bug in the logic of some counters What's the counter? And is "unexpected data detected", is that when files on disk are larger than they're supposed to be, according to the .torrent file?

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@glassez commented on GitHub (Dec 1, 2024):

What's the counter? And is "unexpected data detected", is that when files on disk are larger than they're supposed to be, according to the .torrent file?

This all relates to unexpected counter data provided by the libtorrent:

2024-11-30 17:34 - Unexpected data detected. Torrent: xxxxxx. Data: total_wanted=1792291497 total_wanted_done=1792294912.

As you can see total_wanted_done is larger than total_wanted which is unexpected to be.

@glassez commented on GitHub (Dec 1, 2024): > What's the counter? And is "unexpected data detected", is that when files on disk are larger than they're supposed to be, according to the .torrent file? This all relates to unexpected counter data provided by the libtorrent: >2024-11-30 17:34 - Unexpected data detected. Torrent: xxxxxx. Data: total_wanted=1792291497 total_wanted_done=1792294912. As you can see total_wanted_done is larger than total_wanted which is unexpected to be.

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@unregd commented on GitHub (Dec 2, 2024):

Today I've added 2 torrents as stopped, exact same contents, but different sites/hashes/trackers.
Started one of them, waited till it finished donwloading, force rechecked the other, the "Unexpected data detected" error popped up 9 times, so it's not only happening when moving torrents.

@unregd commented on GitHub (Dec 2, 2024): Today I've added 2 torrents as stopped, exact same contents, but different sites/hashes/trackers. Started one of them, waited till it finished donwloading, force rechecked the other, the "Unexpected data detected" error popped up 9 times, so it's not only happening when moving torrents.

deekerman commented

2026-02-22 02:47:35 -05:00

Author

Owner

@sgmihai commented on GitHub (Nov 8, 2025):

I also encountered this error, after adding a few tens of thousands of torrents for a network/disk benchmark.
Something like ~10-50kb difference. The output disk is zfs, not sure if this is related to zfs.
One time it just stopped updating i/o, not showing updates to download speed at all. But I could close it normally and it was ok when restarted.

@sgmihai commented on GitHub (Nov 8, 2025): I also encountered this error, after adding a few tens of thousands of torrents for a network/disk benchmark. Something like ~10-50kb difference. The output disk is zfs, not sure if this is related to zfs. One time it just stopped updating i/o, not showing updates to download speed at all. But I could close it normally and it was ok when restarted.