Remaining free disk space calculation pauses downloads incorrectly
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Remaining free disk space calculation pauses downloads incorrectly
I regularly have the issue that the remaining free disk space calculation is incorrect and wrongly pauses downloads, when I have more than enough free space.
I'm running the latest version, v5.0.4 on Windows 10. Although I've had this issue for a long time over many versions.
All my downloads are directed to my D: drive, which is a physical, locally attached drive.
I have the minimum free space for temporary downloads and completed downloads both set to 5G (doesn't matter what this is set to, I've tried numerous values and still have the same issue).
And I have all post-processing turned off.
Currently my D: drive has 122GB free (out of 8.18TB), reported by both Windows Explorer and in sabnzbd.
The download that is currently being incorrectly paused is 155789MB in size, 129134MB completed, with 26655MB remaining (26.03GB).
I currently have about 95GB more free disk space than is required, yet sabnzbd still paused the download.
I've seen many people have had this issue over the past years. If it cannot be fixed, then can we please have an option to completely disable the free disk space checks/pausing.
I'm running the latest version, v5.0.4 on Windows 10. Although I've had this issue for a long time over many versions.
All my downloads are directed to my D: drive, which is a physical, locally attached drive.
I have the minimum free space for temporary downloads and completed downloads both set to 5G (doesn't matter what this is set to, I've tried numerous values and still have the same issue).
And I have all post-processing turned off.
Currently my D: drive has 122GB free (out of 8.18TB), reported by both Windows Explorer and in sabnzbd.
The download that is currently being incorrectly paused is 155789MB in size, 129134MB completed, with 26655MB remaining (26.03GB).
I currently have about 95GB more free disk space than is required, yet sabnzbd still paused the download.
I've seen many people have had this issue over the past years. If it cannot be fixed, then can we please have an option to completely disable the free disk space checks/pausing.
Re: Remaining free disk space calculation pauses downloads incorrectly
> The download that is currently being incorrectly paused is 155789MB in size,
For one big download?
Then, rule of thumb, during the download, you need 2 x 155 GB = 310 GB free diskspace: 155 GB for the raw intermediate download, plus 155GB for the resulting stuff. Afterwards, SABnzbd will clean up the intermediate download.
> Currently my D: drive has 122GB free
So: too little.
For one big download?
Then, rule of thumb, during the download, you need 2 x 155 GB = 310 GB free diskspace: 155 GB for the raw intermediate download, plus 155GB for the resulting stuff. Afterwards, SABnzbd will clean up the intermediate download.
> Currently my D: drive has 122GB free
So: too little.
Re: Remaining free disk space calculation pauses downloads incorrectly
As I mentioned, I have all post processing disabled. I am not extracting the archives. When sabnzbd completes a download, it leaves the downloaded files, intact and not extracted. So I don't need double the space for my downloads. The only extra space I need for the intermediate downloads is for each individual file, which in this case is only 1GB.
If the free disk space check is always checking for double the download size, then it is not following our choices in the settings. I set the threshold to pause a download when the free disk space is below 5GB. It is ignoring that setting, because Windows can see I have 95GB free disk space, sabnzbd can see I have 95GB free disk space and sabnzbd can see I have only 26GB remaining to download but it still pauses the download, and that is the bug.
If the free disk space check is always checking for double the download size, then it is not following our choices in the settings. I set the threshold to pause a download when the free disk space is below 5GB. It is ignoring that setting, because Windows can see I have 95GB free disk space, sabnzbd can see I have 95GB free disk space and sabnzbd can see I have only 26GB remaining to download but it still pauses the download, and that is the bug.
Re: Remaining free disk space calculation pauses downloads incorrectly
Yes, the code is always calculating the required free disk space, assuming an unpack is always going to happen.
I looked over the code and can see the issue is in the sabnzbd/assembler .py file, in the diskspace_check() function. But I don't know python to be able to fix it.
Lines 334 to 347 (master branch in the github):
The "if cfg.direct_unpack():" statement checks if Direct Unpack is turned on.
If Direct Unpack is turned off, the code jumps to the "elif nzo.bytes_tried > (nzo.bytes - nzo.bytes_par2) * 0.90" line, where it is just assumed Post Processing will unpack the files.
That elif checks if the amount downloaded so far is at least 90% of (Total Download Size - PAR2 Size). This is the point at which the bug triggers. It then sets the amount of required free disk space in the Completed Folder to the configuration value "Minimum Free Space for Completed Download Folder" + Total Size Of Current Download.
But because Unpack is turned off, that amount of free space is not required. There only needs to be :
free space
The diskspace_check() function needs to check the Processing mode of the Category of the download:
I looked over the code and can see the issue is in the sabnzbd/assembler .py file, in the diskspace_check() function. But I don't know python to be able to fix it.
Lines 334 to 347 (master branch in the github):
Code: Select all
if not full_dir:
complete_free = cfg.complete_free.get_float()
required_space = 0
if cfg.direct_unpack():
# We unpack while we download, so we should check every time
# if the unpack maybe already filled up the drive
required_space = complete_free / GIGI
elif nzo.bytes_tried > (nzo.bytes - nzo.bytes_par2) * 0.90:
# Since only at 100% unpack is started, continue
# downloading until 95% complete before checking
required_space = (complete_free + nzo.bytes) / GIGI
if required_space and complete_dir.free < required_space:
full_dir = complete_dir.path
If Direct Unpack is turned off, the code jumps to the "elif nzo.bytes_tried > (nzo.bytes - nzo.bytes_par2) * 0.90" line, where it is just assumed Post Processing will unpack the files.
That elif checks if the amount downloaded so far is at least 90% of (Total Download Size - PAR2 Size). This is the point at which the bug triggers. It then sets the amount of required free disk space in the Completed Folder to the configuration value "Minimum Free Space for Completed Download Folder" + Total Size Of Current Download.
But because Unpack is turned off, that amount of free space is not required. There only needs to be :
Code: Select all
(nzo.bytes - nzo.bytes_tried) + complete_freeThe diskspace_check() function needs to check the Processing mode of the Category of the download:
- If Download, (nzo.bytes - nzo.bytes_tried) + complete_free
- If +Repair, include some extra % of space for the par repair action.
- If +Unpack or +Delete, include an extra 100% (based on the rule of thumb of x2 space) for the unpack
Re: Remaining free disk space calculation pauses downloads incorrectly
If you consider your point a bug or feature request (and not a support question): https://github.com/sabnzbd/sabnzbd/issues
Re: Remaining free disk space calculation pauses downloads incorrectly
are you running sab on a machine with little storage and then some other app moves it to another place that has storage... if so wouldnt the fix just be run sab where the storage is or move sab complete folder to that storage location?
in sab, click on wrench > show logging and share that sanitized output. ideally curious in your folder and setup.
if you dont feel comfortable sharing that then share specifically:
sab - config > folders
what do you have your sab incomplete and complete folders set to?
sab - config > categories
what do you have it configured to use
fundamentally you need free space for jobs and need double if you are doing incomplete+complete on the same drive and it cant move and has to copy.
and then more if parset/rarset involved due to repair files created and stuff extracted.
depending on the sab version, you can sidestep some of the file space check if your complete folder is set to one thing but your category path is set to something else.. as we previously just used the complete folder from config>folders not the override value of the category path.
in sab, click on wrench > show logging and share that sanitized output. ideally curious in your folder and setup.
if you dont feel comfortable sharing that then share specifically:
sab - config > folders
what do you have your sab incomplete and complete folders set to?
sab - config > categories
what do you have it configured to use
fundamentally you need free space for jobs and need double if you are doing incomplete+complete on the same drive and it cant move and has to copy.
and then more if parset/rarset involved due to repair files created and stuff extracted.
depending on the sab version, you can sidestep some of the file space check if your complete folder is set to one thing but your category path is set to something else.. as we previously just used the complete folder from config>folders not the override value of the category path.
Re: Remaining free disk space calculation pauses downloads incorrectly
Yes and no. The attached drive is 8TB but it often very full. I move/delete files off manually when I need extra space, sometimes while a download in still in progress.
As I identified the issue is indeed a bug in the code (either a bug or an oversight when calculating free space, not checking the unpack choice), I'll open a github issue. Was just reminded to do this, as another download I started this evening was affected - I had 118GB free on the drive, started a 61GB download (unpack turned off still) and it paused with 14GB remaining to download and 65GB free disk space. So plenty of space to finish downloading and not go below the 10G threshold I set in the config.
EDIT: Sorry, I missed you asking what my configuration is set to, so will answer that also now :
sab - config > folders
what do you have your sab incomplete and complete folders set to?
Temporary Downlaod Folder = D:\Usenet\Download
Minimum Free Space for Temporary Download Folder = 5G
Completed Download Folder = D:\Usenet\Complete
Minimum Free Space for Completed Download Folder = 5G
sab - config > categories
what do you have it configured to use
For the Default category, I have Processing=Default. And Folder/Path = blank
For all custom categories I have Processing=Default (even have tried manually setting them to Processing=Download., It makes no difference).
And all custom categories have their Folder/Path = a subfolder of the above Completed Download Folder.
As I identified the issue is indeed a bug in the code (either a bug or an oversight when calculating free space, not checking the unpack choice), I'll open a github issue. Was just reminded to do this, as another download I started this evening was affected - I had 118GB free on the drive, started a 61GB download (unpack turned off still) and it paused with 14GB remaining to download and 65GB free disk space. So plenty of space to finish downloading and not go below the 10G threshold I set in the config.
EDIT: Sorry, I missed you asking what my configuration is set to, so will answer that also now :
sab - config > folders
what do you have your sab incomplete and complete folders set to?
Temporary Downlaod Folder = D:\Usenet\Download
Minimum Free Space for Temporary Download Folder = 5G
Completed Download Folder = D:\Usenet\Complete
Minimum Free Space for Completed Download Folder = 5G
sab - config > categories
what do you have it configured to use
For the Default category, I have Processing=Default. And Folder/Path = blank
For all custom categories I have Processing=Default (even have tried manually setting them to Processing=Download., It makes no difference).
And all custom categories have their Folder/Path = a subfolder of the above Completed Download Folder.
Last edited by acidzero on July 29th, 2026, 5:03 pm, edited 1 time in total.
Re: Remaining free disk space calculation pauses downloads incorrectly
the free space check is done at start of job, so if your deleting stuff out from under sab it wouldnt really know until next job
Re: Remaining free disk space calculation pauses downloads incorrectly
That's not what I saw running from the source code and adding extra logging in the diskspace_check() function. The diskspace_check() function is called at the end of each individual file in the nzb collection. Which is why when a download is manually unpaused, it will paused again at the end of the next file.
And I edited my previous reply with answers to your questions that I initially missed.
And I edited my previous reply with answers to your questions that I initially missed.
Re: Remaining free disk space calculation pauses downloads incorrectly
This is seen in the source file assembler.py, in the def run(self) function :
Code: Select all
# Check if enough disk space is free after each file is done
if file_done and not sabnzbd.Downloader.paused:
self.diskspace_check(nzo, nzf)Re: Remaining free disk space calculation pauses downloads incorrectly
I've reported this now as an Issue on Github : https://github.com/sabnzbd/sabnzbd/issues/3531
Re: Remaining free disk space calculation pauses downloads incorrectly
can you share debug logs of the issue you are seeing just so we can clarify a few things.
in sab, click wrench and set logging level to debug if its not. restart sab and replicate your issue then share the file from wrench>show logging
also if you were not aware of this option:
sab - config > folders > auto resume
> Downloading will automatically resume if the minimum free space is available again.
which will allow sab to just resume when you delete stuff to make room
in sab, click wrench and set logging level to debug if its not. restart sab and replicate your issue then share the file from wrench>show logging
also if you were not aware of this option:
sab - config > folders > auto resume
> Downloading will automatically resume if the minimum free space is available again.
which will allow sab to just resume when you delete stuff to make room
-
BroadSpectrum
- Newbie

- Posts: 1
- Joined: August 8th, 2026, 3:09 pm
Re: Remaining free disk space calculation pauses downloads incorrectly
If you mark the post processing on a job to 'Download' then there should be no unpacking. The free space calculation used to work properly with this setting but now it doesn't. As an example: I have job that is 26GB, with 3GB left to download and 20GB of free space. I have more than enough room to fully download the job but it automatically pauses as soon as it downloads a part because it says I don't have enough space. I don't have any values for 'minimum free space' for temporary or completed download folders. This has worked perfectly until just recently. If I turn on automatically start when there is enough space available it won't start at all.
Direct unpack is not checked.
The logs show that it is trying to decode when it shouldn't be. "Decoding part of ..."
then it hits too little diskspace forcing Pause and says it will resume when there is more than 26GB of free space
I'm running 5.0.4 128e0d0
Direct unpack is not checked.
The logs show that it is trying to decode when it shouldn't be. "Decoding part of ..."
then it hits too little diskspace forcing Pause and says it will resume when there is more than 26GB of free space
I'm running 5.0.4 128e0d0
Re: Remaining free disk space calculation pauses downloads incorrectly
Use 5.1.0RC2
And if needed add feedback in https://github.com/sabnzbd/sabnzbd/issues/3531
Locking this thread.
And if needed add feedback in https://github.com/sabnzbd/sabnzbd/issues/3531
Locking this thread.