starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

3.2.1: disk overload #2781

New issue

Closed

opened 2026-02-21 16:24:27 -05:00 by deekerman · 19 comments

deekerman commented

2026-02-21 16:24:27 -05:00

Owner

Originally created by @vulc on GitHub (Jul 13, 2015).

thats reason why i migrated from utorrent.
Let's go downgrade to 3.2.0.

Originally created by @vulc on GitHub (Jul 13, 2015). thats reason why i migrated from utorrent. Let's go downgrade to 3.2.0. ![image](https://cloud.githubusercontent.com/assets/13315081/8650087/d403743a-2978-11e5-8c11-b9f5ca95fd2a.png)

deekerman closed this issue

2026-02-21 16:24:30 -05:00

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@chrishirst commented on GitHub (Jul 13, 2015):

A translation would be useful.

AND the usual question of WHAT operating system.

@chrishirst commented on GitHub (Jul 13, 2015): A translation would be useful. AND the usual question of WHAT operating system.

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@vulc commented on GitHub (Jul 13, 2015):

Windows 8.1 x64. And this problem on every Windows editions and versions.
I don't know what to exactly need to translate. Disk load 100%.
For example: https://goo.gl/xIvpJJ
It seems - world do not know the nature of this phenomenon and can't solve it.
Just waiting multiple confirmation about problem from other qbit users.

@vulc commented on GitHub (Jul 13, 2015): Windows 8.1 x64. And this problem on every Windows editions and versions. I don't know what to exactly need to translate. Disk load 100%. For example: https://goo.gl/xIvpJJ It seems - world do not know the nature of this phenomenon and can't solve it. Just waiting multiple confirmation about problem from other qbit users.

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@chrishirst commented on GitHub (Jul 13, 2015):

I don't know what to exactly need to translate.

Any of it. All of it. Whatever 'it' is. It could be tomorrows weather forecast for lake Baikal. for all the sense it makes to me.

And I can tell you exactly what causes the disk overload in uTorrent, a badly set up cache and rate limits.

@chrishirst commented on GitHub (Jul 13, 2015): > I don't know what to exactly need to translate. Any of it. All of it. Whatever 'it' is. It could be tomorrows weather forecast for lake Baikal. for all the sense it makes to me. And I can tell you exactly what causes the disk overload in uTorrent, a badly set up cache and rate limits.

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jul 13, 2015):

what is the values you have in "disk write cache size" and "disk cache expiry interval" in the advanced settings of qbt?
What is your download speed?
Is your disk a local disk or a networked one?
Does v3.2.0 have the same problem?

@sledgehammer999 commented on GitHub (Jul 13, 2015): what is the values you have in "disk write cache size" and "disk cache expiry interval" in the advanced settings of qbt? What is your download speed? Is your disk a local disk or a networked one? Does v3.2.0 have the same problem?

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@vulc commented on GitHub (Jul 13, 2015):

2.5 MBytes download speed.
Local disk.
v.3.2.0 don't have this problem!

thank for supporting.

@vulc commented on GitHub (Jul 13, 2015): 2.5 MBytes download speed. Local disk. v.3.2.0 don't have this problem! ![image](https://cloud.githubusercontent.com/assets/13315081/8666053/2ca711c0-29f4-11e5-996d-4b9b04753e94.png) thank for supporting.

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jul 15, 2015):

I have posted to the libtorrent mailing list. Waiting the author's answer.

@sledgehammer999 commented on GitHub (Jul 15, 2015): I have posted to the libtorrent mailing list. Waiting the author's answer.

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@vulc commented on GitHub (Jul 19, 2015):

If author wishes, I would like to give access to my PC (via TeamViewer. ID 724 624 455)

@vulc commented on GitHub (Jul 19, 2015): If author wishes, I would like to give access to my PC (via TeamViewer. ID 724 624 455)

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jul 19, 2015):

Have you enabled pre-allocation?

@sledgehammer999 commented on GitHub (Jul 19, 2015): Have you enabled pre-allocation?

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@vulc commented on GitHub (Jul 19, 2015):

I didn't change any settings from 3.2.0. Just installed 3.2.1 over 3.2.0.
Pre-allocate still disabled.

@vulc commented on GitHub (Jul 19, 2015): I didn't change any settings from 3.2.0. Just installed 3.2.1 over 3.2.0. Pre-allocate still disabled. ![image](https://cloud.githubusercontent.com/assets/13315081/8767564/5476c726-2e69-11e5-9709-0ff097f07e18.png)

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jul 25, 2015):

Can you do these steps:

Start qbt
Locate the qbittorrent.exe entry in the "Processes" tab of Task Manager
When you see the disk overload happening -> right click on the qbt entry and choose "Create Dump"

If the file is small enough email it to me. Otherwise try to upload it somewhere and link here.

email: sledgehammer999 (at) qbittorrent (dot) org

@sledgehammer999 commented on GitHub (Jul 25, 2015): Can you do these steps: 1. Start qbt 2. Locate the `qbittorrent.exe` entry in the "Processes" tab of Task Manager 3. When you see the disk overload happening -> right click on the qbt entry and choose "Create Dump" If the file is small enough email it to me. Otherwise try to upload it somewhere and link here. email: sledgehammer999 (at) qbittorrent (dot) org

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@uLuGaBi commented on GitHub (Sep 3, 2015):

Hello,
I can encounter same problem. Before never had problem: Downloading full speed like 30 mb/s without any issue and uploading was great with sometimes some disk overloads. Those diidn't happened when i'm seeding directly from my NAS using transmission.
Then switched to 3.2.3 64 bits version and now i can't even download. It s always get stucks with disk overload, even directly at start sometimes. Upload become the same, tried reduce speed even to 1 mb/S but still bugging. Tried used seed from 6tb HD or from my NAS (5*3tb RAID 5 connected by gigabit ethernet) but still same problem.
Also tried change cache size or cache expiry time but buffer size don't change.

When i look at statistics read/write overloads are at 0%, no many pending I/O then suddenly I/O come to 1500. This happen every 3/7 minutes and freeze download or upload for one minute which finally kill download speed or upload. If i look at statistics it's finally made an average of less than 1.5 mb/S per second for upload.
Considering line is 25 mb/S capable and it's using gigabit ethernet with 5 HD in raid i find it strange.

@uLuGaBi commented on GitHub (Sep 3, 2015): Hello, I can encounter same problem. Before never had problem: Downloading full speed like 30 mb/s without any issue and uploading was great with sometimes some disk overloads. Those diidn't happened when i'm seeding directly from my NAS using transmission. Then switched to 3.2.3 64 bits version and now i can't even download. It s always get stucks with disk overload, even directly at start sometimes. Upload become the same, tried reduce speed even to 1 mb/S but still bugging. Tried used seed from 6tb HD or from my NAS (5*3tb RAID 5 connected by gigabit ethernet) but still same problem. Also tried change cache size or cache expiry time but buffer size don't change. When i look at statistics read/write overloads are at 0%, no many pending I/O then suddenly I/O come to 1500. This happen every 3/7 minutes and freeze download or upload for one minute which finally kill download speed or upload. If i look at statistics it's finally made an average of less than 1.5 mb/S per second for upload. Considering line is 25 mb/S capable and it's using gigabit ethernet with 5 HD in raid i find it strange.

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@uLuGaBi commented on GitHub (Sep 3, 2015):

Looking at ressources monitor it could be linked to fastresume files:
When it happens there are many tasks writing to BT_Backup fast resume files.
Only disk which seems having lot of I/O is C: This disk is a M2 SSD disk and i'm running thousands torrents but only 2 active downloads and 1 active upload
I also sent you the dmp file

@uLuGaBi commented on GitHub (Sep 3, 2015): Looking at ressources monitor it could be linked to fastresume files: When it happens there are many tasks writing to BT_Backup fast resume files. Only disk which seems having lot of I/O is C: This disk is a M2 SSD disk and i'm running thousands torrents but only 2 active downloads and 1 active upload I also sent you the dmp file

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Sep 4, 2015):

@uLuGaBi if you can test v3.3.0beta builds. The v3.2.x series have almost come to an end. v3.3.x has major core refactoring.
v3.3.0beta: http://www.fosshub.com/qBittorrent.html

@sledgehammer999 commented on GitHub (Sep 4, 2015): @uLuGaBi if you can test v3.3.0beta builds. The v3.2.x series have almost come to an end. v3.3.x has major core refactoring. v3.3.0beta: http://www.fosshub.com/qBittorrent.html

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@uLuGaBi commented on GitHub (Sep 4, 2015):

Bit busy for this week so before testing:
Is it really unstable ?
I used the QT5version, not gonna create problem since i see it's QT 4.8.7?
Had many GUI problems with 32 bits version when passing 3000 torrents (slowness, no more able to sort torrents, not able to perform actions like moving or resume files), do you think it will continue on this version rather than the 64 bits one?

@uLuGaBi commented on GitHub (Sep 4, 2015): Bit busy for this week so before testing: Is it really unstable ? I used the QT5version, not gonna create problem since i see it's QT 4.8.7? Had many GUI problems with 32 bits version when passing 3000 torrents (slowness, no more able to sort torrents, not able to perform actions like moving or resume files), do you think it will continue on this version rather than the 64 bits one?

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Sep 4, 2015):

3.3.0 is nearing release. It is very stable. Actually it is called beta/unstable just because we keep adding features and tweak things.
No problem between qt5 and qt4. Your columns and window sizes maybe different but once you go back to qt5 they should return(the settings are saved in different locations for qt5).
The GUI issues should be non-existent with 3.3.0.

@sledgehammer999 commented on GitHub (Sep 4, 2015): 3.3.0 is nearing release. It is very stable. Actually it is called beta/unstable just because we keep adding features and tweak things. No problem between qt5 and qt4. Your columns and window sizes maybe different but once you go back to qt5 they should return(the settings are saved in different locations for qt5). The GUI issues should be non-existent with 3.3.0.

deekerman commented

2026-02-21 16:24:31 -05:00

Author

Owner

@uLuGaBi commented on GitHub (Sep 5, 2015):

But no 64 bits version?

@uLuGaBi commented on GitHub (Sep 5, 2015): But no 64 bits version?

deekerman commented

2026-02-21 16:24:32 -05:00

Author

Owner

@chrishirst commented on GitHub (Sep 5, 2015):