Check available space in incomplete download directory before downloading there #15801

New issue

Open

opened 2026-02-22 02:30:36 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 02:30:36 -05:00

Owner

Originally created by @sotiris-bos on GitHub (May 28, 2024).

Suggestion

There should be a check of free space of the incomplete download dir before the client starts to download.

Use case

Some of us use a small temporary location to download torrents before moving them to a larger, slower pool.

Some torrents might be too big for the temporary location. These should probably be downloaded directly to the save path instead of the incomplete directory. Currently, they just error out when the incomplete directory fills up.

Extra info/examples/attachments

No response

Originally created by @sotiris-bos on GitHub (May 28, 2024). ### Suggestion There should be a check of free space of the incomplete download dir before the client starts to download. ### Use case Some of us use a small temporary location to download torrents before moving them to a larger, slower pool. Some torrents might be too big for the temporary location. These should probably be downloaded directly to the save path instead of the incomplete directory. Currently, they just error out when the incomplete directory fills up. ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Temp folder

labels

2026-02-22 02:30:36 -05:00

deekerman commented

2026-02-22 02:30:41 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 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 ❤ reactions in 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:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 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:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. 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:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**