Skip to content
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

when you disable some disks, "errored" files flood errorred category slowly instead of checking if the whole media is available. #20816

Open
estatistics opened this issue May 7, 2024 · 1 comment

Comments

@estatistics
Copy link

estatistics commented 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
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant