mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Partial downloads (that were migrated from 3.3.16) give IO errors when a chunk of a Not Downloaded file is being read. #6478
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#6478
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @EraYaN on GitHub (Nov 30, 2017).
Please provide the following information
qBittorrent version and Operating System
4.0.1 on Windows 10 x64 ver . 1709
What is the problem
And the file path points to a file that is "Not Downloaded" state in the content tab, so it would seem logical that it can't find this file, I wont if it properly communicates this to other peers. Also the torrent happily continues seeding (as mentioned in an other issue. In this case that is the wanted behaviour.
What is the expected behavior
Don't try to read non existent files that you know upfront will not exist.
Steps to reproduce
Migrate partial download (finished but with some files marked "Don't Download") to 4.0.1 (in one go, skip 4.0.0 And wait until seeding begins (actual upload). The problem is probably when a peer requests a chunk you don't have.
Extra info(if any)
Happen for multiple torrents.