mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Error - no work Pre-allocate disk #17127
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#17127
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 @l-n0-0b on GitHub (Aug 30, 2025).
Suggestion
Linux Arch
flatpak
qbit v5.1.2
Error - no work "+Pre-allocate disk space" for all files.
The disk is filling up gradually anyway. The disk size does not show immediately with the size of the occupied files, and the disk space changes (decreases) as it loads.
In btrfs, ext4, ntfs,exfat file systems...
20% download - **File error alert. *.iso.!qB) error: There is no free space left on the device"
Use case
What would have been like before, when the "Pre-allocate disk space for all files" feature was enabled, the file immediately occupied the full size. In fact, downloads interfere with each other because they don't have the full size and don't fit on the disk either.
Extra info/examples/attachments
No response
@qBittUser commented on GitHub (Aug 30, 2025):
If you're not asking for any new feature and there's error or regression, then you're supposed to create a proper issue report.
You mean a specific older qBittorrent version worked fine?
Try official image instead of anything else.
@l-n0-0b commented on GitHub (Aug 30, 2025):
How can I add the required "log" if it's empty and everything is fine with the log?
Yes, but I don't remember the version, either 5.0.5 or 5.1.0
I always thought that flatpak was the most official and clean version, as it was isolated from the system itself.
@qBittUser commented on GitHub (Aug 30, 2025):
Then you don't provide it and instead write that it's enabled, but empty. If it's not enabled or you have changed it's default location, then it will be visible in your preferences settings file.
If you can reproduce your issues with different installer, then maybe it can be used to provide you a workaround and make it easier for others to guess right what's causing issues.
AppImage file for Linux, mentioned in official qBit website and downloadable from SourceForge might have less issues.
If you don't have enough space on disk, then get bigger disk that's specifically intended only for your downloads to avoid any extra unexpected issues.
@l-n0-0b commented on GitHub (Aug 30, 2025):
in the sense that the log is empty, that the log is error-free.
Why are you blaming me for the reasons?
Here is the Log "qBittorrent termination initiated" after exiting the program - I press exit - and the exit freezes.
And everything else in the log is useless, this description is ordinary, the program did this and that with files.
I can't reinstall the program because it contains data and settings.
It seems to me that the whole problem is that modern programmers don't use their programs thoroughly.
Me and We suggested solutions to the problem - add a "queue" for these actions.
This is your functionality of the program - "report an error if there is no place", "move to another location" and other subtleties. (it would also be nice to add a queue for speed).
You think I need it, but I just want the program to get better. If you don't want to, it's your business, I've already written about all the problems I've encountered.
Sometimes it seems to me that I'm the only one using all the programs and encountering errors in them.
You just messed up something a lot in the last update, probably. @_@
@l-n0-0b commented on GitHub (Aug 30, 2025):
You know, that's not even the point, that's not the question. And the question is that the process is wrong - "in the stop state", I press "start" and suddenly it starts creating a "temporary file", writes that there is no space, this "temporary file" needs to be moved somewhere or deleted (the download content folder, without the download t-file itself, you can't delete it, there is no such item). This means that you need to move and it will take so long to move that even if there is a 5mb file, it takes as long as if it were 50GB.
@qBittUser commented on GitHub (Aug 30, 2025):
Providing tips, ideas, random guesses and workarounds and asking for more info to vague issues how others can reliably reproduce isn't same as blaming.
If you start reading various issue reports and feature requests, then majority are labeled correctly and I believe there's higher chance to get things confirmed and fixed if things are written better.
Some users try to download things to same drive where's their system or have incompatible file system or some external drive that's causing similar issues, but never mention about it in opening post how, what and where exactly have they tried to download.
Can't these be copied somewhere else?
What about another device, to recheck if flatpak and AppImage work differently?
I do. Well if no more info and if no one else tries to confirm and explain your issue, then I'll try luck to reproduce this in couple days.
@l-n0-0b commented on GitHub (Aug 30, 2025):
https://github.com/qbittorrent/qBittorrent/issues/23188#issuecomment-3239513008
I've added more here.
Maybe it will be clearer. Let me explain it again... there are a lot of downloads, for example 10, and they, for example, have 0 speeds or do not turn on immediately (by the way, the queue itself in the program spoils everything, for some reason the speeds drop than usual and the wrong ones swing - I still haven't figured it out),
for example, I'm afk (moved away from the computer), and here I am I come back, and there half of the downloads are red with this error, because the speed has increased on one of the downloads and it has taken up space and there was not enough space for the others.
As a result, there was not enough space for all downloads, as each one inherited.
And now one has to be moved to another place - for a very long time, each one.
Because if you transfer all the errors at once, then everything will hang.
It's a whole process where everything clings to one another.
@l-n0-0b commented on GitHub (Aug 30, 2025):
ON - Add to top of queue
OFF - Do no start the download automatically
ON - stop condition: Files Checked
ON - Pre-allocate disk space for all files
ON - Append .!qB extension to incomplete files
added downloads to the program.
Button START.
out of 2 out of 10, the speed is normal, the rest have 0
I Gone - I come (AFK)
3 out of 10 downloaded normally, 4 - 20% with an error, the other 5 pcs - immediately with an error.
I select 8 and moved it to another disk - everything freezes download and all program.
8.But the hovering at this moment is not permanent. Random.
@l-n0-0b commented on GitHub (Aug 30, 2025):
I will also add that what I am describing is not a bug, but simply a malfunction of the function. This creates a lot of confusion. It turns out that not one of the downloads creates the full file size and because of this they do not see when there is no space. And this already leads to other problems in other topics that I have described, but they are unrelated, because downloads can be moved in other ways. (the last points are for example).
@l-n0-0b commented on GitHub (Oct 20, 2025):
### The error is still there.
File error alert. File: ".!qB". Reason: "(.!qB) error: There is no free space left on the device"*
The program is most likely frozen as well (meaning it's downloading, but won't close properly).
Since downloads start automatically when speed increases, downloads interfere with each other. (It's a good thing that "paused downloads" don't immediately take up disk space after being added to the queue, although this requires some strange program configuration.)
I still don't understand how the download queue works; it essentially pushes downloads with good speeds down, creating a mess, making things even worse.
With this option, without a queue, it's impossible, for example, to enable all downloads to start, since the program doesn't understand the remaining disk space. As a result, one download will be 70%, while the second download will be 20%, and both will "freeze."
Moving a "broken" download sometimes works fine, but sometimes it freezes.