mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Don't pause when an I/O error occurs #1167
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#1167
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 @Yehudi99 on GitHub (Feb 4, 2014).
if a file with a total length greater than 260 characters would be created, the following occurs (extract from the execution log
04/02/2014 19:37:46 - An I/O error occurred, 'Queen - Collection 1967-2011 57 ALBUMS + 65 SINGLES --TBS' paused.
04/02/2014 19:37:46 - Reason: Queen - Collection 1967-2011 57 ALBUMS + 65 SINGLES --TBS file (C:/Users/xxx/Documents/___Intray/__torrent/downloading\Queen - Collection 1967-2011 57 ALBUMS + 65 SINGLES --TBS\Albums\2009 - Queen - Singles Collection Vol. 2 [Remaster 13CD]\1980 CD06 Flash s Theme (CDS2009 Singles Collection Vol 2)(320)\Artwork\Papersleeve Front.jpg) error: The filename or extension is too long
In this case surely the download should continue and only this file should be paused? I looked for a setting to control this behaviour but couldn't find one ...
Otherwise, great job. Just uninstalled uTorrent.
@sledgehammer999 commented on GitHub (Feb 4, 2014):
This is a little difficult to fix. How does utorrent handle this case?
Btw what filesystem are you using?
@sledgehammer999 commented on GitHub (Feb 4, 2014):
Also what qbt version and what OS?
@Yehudi99 commented on GitHub (Feb 5, 2014):
Hi sledgehammer 99 ...
Windows 7 fully patched and updated, qbt 3.1.5 (the latest off ninite.com a couple of days ago); NTFS filesystem .
I understand this one might be a bit tricky, but rather than pause the whole download – why not just pause the file (which the error message identified) and carry on with the rest of the download?
By the way – I think I’ve largely solved this problem by changing my dl directory to
M:\t
But the fact remains that qbt is not degrading gracefully, in my oh so humble C# guy kind of way.
Best regards
Jon
From: sledgehammer999 [mailto:notifications@github.com]
Sent: Wednesday, 5 February 2014 5:58 AM
To: qbittorrent/qBittorrent
Cc: Yehudi99
Subject: Re: [qBittorrent] [Wishlist] Don't pause when an I/O error occurs (#1381)
Also what qbt version and what OS?
—
Reply to this email directly or view it on GitHub https://github.com/qbittorrent/qBittorrent/issues/1381#issuecomment-34093812 . https://github.com/notifications/beacon/6582691__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNzA3MzA2NCwiZGF0YSI6eyJpZCI6MjQ4ODIwMjl9fQ==--1080bf06aab0682e4c7058a547d130435f238ae0.gif
@popman commented on GitHub (Feb 9, 2014):
Similarly, when downloading a large (4GB+) file to a filesystem that doesn't support it, like FAT32 the file should be split into smaller chunks to avoid stalling the download, like how Transmission handles the case.
for example, BigFile.extention (4GB+) would be split into;
BigFile.extention.66600 (1GB)
BigFile.extention.66601 (1GB)
BigFile.extention.66602 (1GB)
etc...
Moving the files to a drive without this issue causes them to be joined again, and vice versa.
@xavier2k6 commented on GitHub (May 23, 2025):
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:
Please select/click the 👍 &/or ❤
reactionsin the original/opening post of this ticket.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:
DO NOT:
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)