Pre-allocation progress bar #5081

New issue

Open

opened 2026-02-21 17:39:26 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 17:39:26 -05:00

Owner

Originally created by @starvedhorror on GitHub (Jan 1, 2017).

Is it possible to add a progress bar for the file pre-allocation process? I've been using tixati before & it's the only feature i'm really missing, because pre-allocating big files on a regular hdd takes quite a lot of time & with such high disk utilization it's almost impossible to do anything else. (It basically does 'Disk overloaded 100% utorrent-style) Having at least an estimate would be nice.

Originally created by @starvedhorror on GitHub (Jan 1, 2017). Is it possible to add a progress bar for the file pre-allocation process? I've been using tixati before & it's the only feature i'm _really_ missing, because pre-allocating big files on a regular hdd takes quite a lot of time & with such high disk utilization it's almost impossible to do anything else. (It basically does 'Disk overloaded 100% utorrent-style) Having at least an estimate would be nice.

deekerman added the

Feature request

label

2026-02-21 17:39:26 -05:00

deekerman commented

2026-02-21 17:39:29 -05:00

Author

Owner

@fbriere commented on GitHub (May 6, 2017):

Unfortunately, I don't think this is currently possible with libttorrent. (See #508 for a similar request.)

@fbriere commented on GitHub (May 6, 2017): Unfortunately, I don't think this is currently possible with libttorrent. (See #508 for a similar request.)

deekerman commented

2026-02-21 17:39:30 -05:00

Author

Owner

@starvedhorror commented on GitHub (May 18, 2020):

From what i understand, certain improvements have been made to a similar issue since i've opened this one.

https://github.com/qbittorrent/qBittorrent/pull/8716/commits
https://github.com/qbittorrent/qBittorrent/issues/508

It looks like there is still no progress on this issue.

https://github.com/arvidn/libtorrent/issues/2923

Unfortunately i know nothing about coding, so i can't really suggest any potential solution for it. However i'm curious if it's possible to perhaps implement similar status change for pre-allocation progress now? It can still be quite frustrating waiting for a big torrent to pre-allocate all it's files, since it stalls all other active ones until the process is done, with an occasional brief bursts of download activity.

@starvedhorror commented on GitHub (May 18, 2020): From what i understand, certain improvements have been made to a similar issue since i've opened this one. https://github.com/qbittorrent/qBittorrent/pull/8716/commits https://github.com/qbittorrent/qBittorrent/issues/508 It looks like there is still no progress on this issue. https://github.com/arvidn/libtorrent/issues/2923 Unfortunately i know nothing about coding, so i can't really suggest any potential solution for it. However i'm curious if it's possible to perhaps implement similar status change for pre-allocation progress now? It can still be quite frustrating waiting for a big torrent to pre-allocate all it's files, since it stalls all other active ones until the process is done, with an occasional brief bursts of download activity.

deekerman commented

2026-02-21 17:39:30 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 23, 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 23, 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.)**