mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
when you disable some disks, "errored" files flood errorred category slowly instead of checking if the whole media is available. #15750
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#15750
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 @estatistics on GitHub (May 7, 2024).
qBittorrent & operating system versions
qBittorrent v4.6.3 (64-bit)
linux debian trixie/sid
What is the problem?
when you disable some disks, "errored" files flood errorred category slowly instead of checking if the whole media is available.
So you have 5000 torrents.
2000 of them are in sdc1
For some reason, you disconnect sdc1,
it will took almost 10 or more minutes to files to move to error status.
Also, a lot of message flood qbittorent (if active).
Suggestions:
a) A better manager of error messages - if media is disconnected, it is enough to say sdc1 was not found, files will be errored instead of 2000 messages.
b) it appears that qbittorent do not check if the "basic" media is connected instead checks every one file. I can understand that there are virtual connected devices and other complicated things. However, somehow this must be solved.
c) an option for errorred files to automatically paused in order to stop flooding with error messages
After some time qbit is crashing... i think it cant handle 2000 error messages even i have disabled messages?
Steps to reproduce
No response
Additional context
No response
Log(s) & preferences file(s)
No response
@estatistics commented on GitHub (May 7, 2024):
in same logic, checking of files happen serially, one per time, even if files are in 20 different drives. Therefore, checking can be very quick if files on different media are checked concurrently.