-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fast Resume loses some custom torrent folder names; correcting it goes to 0% downloaded, requires manual recheck #468
Comments
hmm wonder if this is related to the libtorrent sparse flag bug try the experimental builds on the forum |
I think I have similar situation. I have fully download content. It is possible to force recheck data and share again without redownloading it? It is possible to safely change location of downloaded file? |
Is this still happening with 3.0.11? |
confirmed with nightly looks like a libtorrent issue with quick-recheck |
Can you link to the problematic .torrent file? |
We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0). |
qBittorrent 3.0.8
When starting qBittorrent, Fast Resume "succeeds" with torrents per the log, but some multi-file torrents have had their folder name reset to the default from the torrent file rather than the name I set (and where the files are located).
When a peer connects to download a piece, the following error and log entries are generated:
(FILE_PATH/DEFAULT_FOLDER_NAME\SOME_FILENAME)
error: The system cannot find the path specified
And then the torrent is paused (still showing 100% downloaded).
To correct the issue, I rename the top folder in the torrent on the Transfers/Content tab.
As soon as I rename the folder, the "Done" column is changed to 0.0%.
If I simply try to resume the torrent, it will try to redownload it, so I have to do a Force Recheck first.
This problem is presently effecting one torrent on my list, albeit a large one. Following the above procedure to recover the correct state for torrent requires a lot of file I/O and time to correct, as well as several manual steps for each torrent.
An alternative temporary fix is to delete the torrent from the list, then reopen or redownload the torrent file, selecting the folder name and the "Skip Hash Check" option in the Add New Torrent dialog. This sometimes prevents a recheck (although, and this is a separate issue, some torrents are rechecked anyway..., not sure why). The particular torrent on my last at present exhibiting the issue gets rechecked even this way.
Upon restarting qBittorrent again in either case, the same torrents have lost their custom folder names and repeat this issue exactly.
The custom folder names lost all happen to include Unicode characters, although other torrent folder names with Unicode characters are not lost. A large percentage of my custom folder names contain Unicode characters. I don't know if this is relevant at all, but it does occur to me that it may be a string handling bug with certain codepoint ranges.
The text was updated successfully, but these errors were encountered: