Pre-allocate disk space for individual torrents #14069

New issue

Open

opened 2026-02-22 00:39:32 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-22 00:39:32 -05:00

Owner

Originally created by @Snake883 on GitHub (Dec 5, 2022).

Suggestion

Instead of preallocating disk space for all torrents, I only want to preallocate for some torrents

Use case

I don't want to preallocate and use up all my storage space for very slow torrents or torrents that have sporadic availability (poor health/availability). Also, I've started downloads with seeders, only to end up with a dead torrent. I don't want to preallocate storage for these torrents.

I rather have the option to start some torrents non-preallocated, and then change to preallocated if I determine the download is fast enough, and the torrent is healthy.

Unfortunately I won't know the health of the torrent until after the download has started, and sometimes I have to wait a few days to determine the availability.

Extra info/examples/attachments

No response

Originally created by @Snake883 on GitHub (Dec 5, 2022). ### Suggestion Instead of preallocating disk space for all torrents, I only want to preallocate for some torrents ### Use case I don't want to preallocate and use up all my storage space for very slow torrents or torrents that have sporadic availability (poor health/availability). Also, I've started downloads with seeders, only to end up with a dead torrent. I don't want to preallocate storage for these torrents. I rather have the option to start some torrents non-preallocated, and then change to preallocated if I determine the download is fast enough, and the torrent is healthy. Unfortunately I won't know the health of the torrent until after the download has started, and sometimes I have to wait a few days to determine the availability. ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Waiting upstream

Libtorrent

labels

2026-02-22 00:39:32 -05:00

deekerman commented

2026-02-22 00:39:39 -05:00

Author

Owner

@thalieht commented on GitHub (Dec 6, 2022):

for individual files

files or torrents? In post body you say torrents. Anyway both of them are up to libtorrent.

@thalieht commented on GitHub (Dec 6, 2022): >for individual files files or torrents? In post body you say torrents. Anyway both of them are up to libtorrent.

deekerman commented

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

Author

Owner

@Snake883 commented on GitHub (Dec 7, 2022):

files or torrents?

For individual torrents. I made the correction in my previous post, thank you.

@Snake883 commented on GitHub (Dec 7, 2022): > files or torrents? For individual torrents. I made the correction in my previous post, thank you.

deekerman commented

2026-02-22 00:39: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.)**