It leaves so many files which I have marked as not to download. #4065

Closed
opened 2026-02-21 17:06:52 -05:00 by deekerman · 26 comments
Owner

Originally created by @laichiaheng on GitHub (Mar 18, 2016).

It happens so many times that I have to delete them manually.

Originally created by @laichiaheng on GitHub (Mar 18, 2016). It happens so many times that I have to delete them manually.
Author
Owner

@m5skeet commented on GitHub (Mar 19, 2016):

same thing happening on every torrent i download ever since 3.3.3

@m5skeet commented on GitHub (Mar 19, 2016): same thing happening on every torrent i download ever since 3.3.3
Author
Owner

@DerekTurtleRoe commented on GitHub (Mar 19, 2016):

@laichiaheng @m5skeet You guys should provide more information than that, like a list of the files that you were downloading, OS version, settings used, etc.

@DerekTurtleRoe commented on GitHub (Mar 19, 2016): @laichiaheng @m5skeet You guys should provide more information than that, like a list of the files that you were downloading, OS version, settings used, etc.
Author
Owner

@laichiaheng commented on GitHub (Mar 19, 2016):

@vgturtle127
OS: Ubuntu 14.04.4LTS
settings: default
qbittorrent 3.3.3

@laichiaheng commented on GitHub (Mar 19, 2016): @vgturtle127 OS: Ubuntu 14.04.4LTS settings: default qbittorrent 3.3.3
Author
Owner

@DerekTurtleRoe commented on GitHub (Mar 19, 2016):

@laichiaheng I am on 64-bit Windows 10 Pro with qBittorrent 3.3.3 and everything works OK here. Maybe a Linux-only issue?

@DerekTurtleRoe commented on GitHub (Mar 19, 2016): @laichiaheng I am on 64-bit Windows 10 Pro with qBittorrent 3.3.3 and everything works OK here. Maybe a Linux-only issue?
Author
Owner

@m5skeet commented on GitHub (Mar 20, 2016):

OS:Windows 10 home 64 bit
settings:default
qb 3.3.3
wasd
dsaw

atleast for me it's random how many other not selected it download's sometimes like above or other times it downloads all

idk if this is the same issue the guy above is having

@m5skeet commented on GitHub (Mar 20, 2016): OS:Windows 10 home 64 bit settings:default qb 3.3.3 ![wasd](https://cloud.githubusercontent.com/assets/17941243/13904390/43407f46-ee9f-11e5-8fe8-3102cdc2ca38.PNG) ![dsaw](https://cloud.githubusercontent.com/assets/17941243/13904392/46f581cc-ee9f-11e5-952e-b6d8b3846b26.PNG) atleast for me it's random how many other not selected it download's sometimes like above or other times it downloads all idk if this is the same issue the guy above is having
Author
Owner

@Levdbas commented on GitHub (Mar 21, 2016):

Same here. W10, Qbittorrent 3.3.3. I select one file to download and everything got downloaded instead.

@Levdbas commented on GitHub (Mar 21, 2016): Same here. W10, Qbittorrent 3.3.3. I select one file to download and everything got downloaded instead.
Author
Owner
@ghost commented on GitHub (Mar 21, 2016): https://github.com/qbittorrent/qBittorrent/wiki/Frequently-Asked-Questions#I_configured_qBittorrent_to_not_download_some_files_in_a_torrent_but_they_still_appear_on_my_hard_disk_why_is_that
Author
Owner

@DerekTurtleRoe commented on GitHub (Mar 21, 2016):

@gwarser Is there a better way to implement that? I mean, I feel like even just asking the user which files to keep or something would be better than "that's how it works".

This isn't a libtorrent limitation, is it?

@DerekTurtleRoe commented on GitHub (Mar 21, 2016): @gwarser Is there a better way to implement that? I mean, I feel like even just asking the user which files to keep or something would be better than "that's how it works". This isn't a libtorrent limitation, is it?
Author
Owner

@laichiaheng commented on GitHub (Mar 21, 2016):

@gwarser You mean the option in qbittorrent is useless?

@laichiaheng commented on GitHub (Mar 21, 2016): @gwarser You mean the option in qbittorrent is useless?
Author
Owner

@ghost commented on GitHub (Mar 22, 2016):

In older versions all unwanted files are hidden inside .unwanted folder.
In future they probably be stored in one "data" file (utorrent way).

@ghost commented on GitHub (Mar 22, 2016): In older versions all unwanted files are hidden inside `.unwanted` folder. In future they probably be stored in one "data" file (utorrent way).
Author
Owner

@DartMik commented on GitHub (Mar 27, 2016):

Same problem. Win10 64 bit. Has anyone found a solution to the problem ? It is inconvenient to work with the program because of this ...

@DartMik commented on GitHub (Mar 27, 2016): Same problem. Win10 64 bit. Has anyone found a solution to the problem ? It is inconvenient to work with the program because of this ...
Author
Owner

@tp0 commented on GitHub (Mar 28, 2016):

The removal of the .unwanted folder in 3.3.3 is what the problem here is. Previously non-downloaded files were put there, it was hidden folder so you may have not known they were there. Apparently there were problems with this folder and in some cases the files there were not always removed by qBittorrent. Couple of years ago there was also a poll on the forums and majority wanted to remove the functionality.

Not sure why this change now, perhaps something to do with libtorrent. Also, last year a support for "part" or "data" files (like in uTorrent) was added in libtorrent and somewhere the dev(s) indicated this would implemented in qBittorent in future.

  • The files are not actually downloaded completely and they do not take much space. See @gwarser's link. File managers may report a non-downloaded file taking e.g. 1 GB, but that's false. You can see the real size by checking "size on disk" size in file properties and it is few megabytes tops.
  • This folder still seems to be created for torrents that were added previously, even if you re-add them into a different folder.
  • I recommend turning on Options > Downloads > Append .!qB extension to incomplete files. Why this isn't enabled by default now? This probably would make it a lot less confusing for users. And generally less annoying. (#5023)

ps. Workaround for Linux users: do this in the folder: ls *.\!qB >> .hidden. This creates .hidden file which can be used to hide non-dotted files and folders, should work in most file managers.

@tp0 commented on GitHub (Mar 28, 2016): The removal of the `.unwanted` folder in 3.3.3 is what the problem here is. Previously non-downloaded files were put there, it was hidden folder so you may have not known they were there. Apparently there were problems with this folder and in some cases the files there were not always removed by qBittorrent. Couple of years ago [there was also a poll](https://qbforums.shiki.hu/index.php/topic,2294.0.html) on the forums and majority wanted to remove the functionality. Not sure why this change now, perhaps something to do with libtorrent. Also, last year a support for "part" or "data" files (like in uTorrent) was added in libtorrent and somewhere the dev(s) indicated this would implemented in qBittorent in future. - The files are not actually downloaded completely and they do not take much space. See @gwarser's link. File managers may report a non-downloaded file taking e.g. 1 GB, but that's false. You can see the real size by checking "size on disk" size in file properties and it is few megabytes tops. - This folder still seems to be created for torrents that were added previously, even if you re-add them into a different folder. - I recommend turning on **Options > Downloads > Append .!qB extension to incomplete files**. Why this isn't enabled by default now? This probably would make it a lot less confusing for users. And generally less annoying. (#5023) ps. Workaround for Linux users: do this in the folder: `ls *.\!qB >> .hidden`. This creates .hidden file which can be used to hide non-dotted files and folders, should work in most file managers.
Author
Owner

@DerekTurtleRoe commented on GitHub (Mar 28, 2016):

@tp0 OK, that clears some stuff up.

I agree appending an extension is way less confusing.

Also, are we on the latest libtorrent?

What is the discrepancy between file sizes? Is qBittorrent calculating something incorrectly, or is it a OS to application issue?

So if you download something with the newest version of qBittorrent now it won't create the .unwanted directory, but if you had previously downloaded something with the .unwanted directory it just stays there? I guess I am questioning my understanding of the issue now.

I thought that the issue was that the files were downloaded into the .unwanted directory because of a bug, or regression. And as such, they were taking up space and showing up on peoples hard drives when the files were completed. But I guess the issue is older downloads and newer downloads are conflicting? Should we have a "clear all temporary files" option or something? Not sure...

@DerekTurtleRoe commented on GitHub (Mar 28, 2016): @tp0 OK, that clears some stuff up. I agree appending an extension is way less confusing. Also, are we on the latest libtorrent? What is the discrepancy between file sizes? Is qBittorrent calculating something incorrectly, or is it a OS to application issue? So if you download something with the newest version of qBittorrent now it won't create the .unwanted directory, but if you had previously downloaded something with the .unwanted directory it just stays there? I guess I am questioning my understanding of the issue now. I thought that the issue was that the files were downloaded into the .unwanted directory because of a bug, or regression. And as such, they were taking up space and showing up on peoples hard drives when the files were completed. But I guess the issue is older downloads and newer downloads are conflicting? Should we have a "clear all temporary files" option or something? Not sure...
Author
Owner

@tp0 commented on GitHub (Mar 28, 2016):

Also, are we on the latest libtorrent?

Probably not yet as there's a test version: https://qbforums.shiki.hu/index.php/topic,4113.0.html

What is the discrepancy between file sizes? Is qBittorrent calculating something incorrectly, or is it a OS to application issue?

Allocated space vs. actually utilized space... how disks work, so not a qB issue. In Windows, the explorer file properties window shows both, on Linux du -h shows size on disk.

So if you download something with the newest version of qBittorrent now it won't create the .unwanted directory, but if you had previously downloaded something with the .unwanted directory it just stays there? I guess I am questioning my understanding of the issue now.

At least if it is the same torrent. Happened with one I tested. I removed it (not data) from qBittorrent and added into a new folder. qBittorrent must save information of these somewhere and this is probably intended to not create conflicts.

I thought that the issue was that the files were downloaded into the .unwanted directory because of a bug, or regression. And as such, they were taking up space and showing up on peoples hard drives when the files were completed. But I guess the issue is older downloads and newer downloads are conflicting?

I'm not that sure about the past bugs, but when I searched the forums something related to those files not being removed came up. Or perhaps it was just people being confused about the files generally. At least currently when completely removing (with data) multifile torrents with a folder included in the torrent file list, the whole folder will be removed (unless there is a file not belonging to the torrent itself, qB is smart enough to take that into account, the partial files we're now talking about now do not count as such).

Should we have a "clear all temporary files" option or something? Not sure...

(Not temporary - if a piece from file2 is needed to get 100% of file1, then user needs it for as long as he wants to have 100% of file1.) I guess a clearing function could be useful in cases where user has removed only the torrent (but not with data) via qB, and thus the partial files remain on the disk. I don't know if this even technically possible, how can qB keep record of this etc.

@tp0 commented on GitHub (Mar 28, 2016): > Also, are we on the latest libtorrent? Probably not yet as there's a test version: https://qbforums.shiki.hu/index.php/topic,4113.0.html > What is the discrepancy between file sizes? Is qBittorrent calculating something incorrectly, or is it a OS to application issue? Allocated space vs. actually utilized space... how disks work, so not a qB issue. In Windows, the explorer file properties window shows both, on Linux `du -h` shows size on disk. > So if you download something with the newest version of qBittorrent now it won't create the .unwanted directory, but if you had previously downloaded something with the .unwanted directory it just stays there? I guess I am questioning my understanding of the issue now. At least if it is the same torrent. Happened with one I tested. I removed it (not data) from qBittorrent and added into a new folder. qBittorrent must save information of these somewhere and this is probably intended to not create conflicts. > I thought that the issue was that the files were downloaded into the .unwanted directory because of a bug, or regression. And as such, they were taking up space and showing up on peoples hard drives when the files were completed. But I guess the issue is older downloads and newer downloads are conflicting? I'm not that sure about the past bugs, but when I searched the forums something related to those files not being removed came up. Or perhaps it was just people being confused about the files generally. At least currently when completely removing (with data) multifile torrents with a folder included in the torrent file list, the whole folder will be removed (unless there is a file not belonging to the torrent itself, qB is smart enough to take that into account, the partial files we're now talking about now do not count as such). > Should we have a "clear all temporary files" option or something? Not sure... (Not temporary - if a piece from file2 is needed to get 100% of file1, then user needs it for as long as he wants to have 100% of file1.) I guess a clearing function could be useful in cases where user has removed only the torrent (but not with data) via qB, and thus the partial files remain on the disk. I don't know if this even technically possible, how can qB keep record of this etc.
Author
Owner

@DerekTurtleRoe commented on GitHub (Mar 28, 2016):

@tp0 OK, that helps a lot. Thanks.

Some refactoring and code checking may be in order on my end...

@DerekTurtleRoe commented on GitHub (Mar 28, 2016): @tp0 OK, that helps a lot. Thanks. Some refactoring and code checking may be in order on my end...
Author
Owner
@slr commented on GitHub (Apr 1, 2016): see also https://github.com/qbittorrent/qBittorrent/issues/4914 and https://github.com/qbittorrent/qBittorrent/issues/4760
Author
Owner

@DartMik commented on GitHub (Apr 1, 2016):

О, будь добр, растолкуй мне суть проблемы по этому вопросу и пути её решения на великом и могучем) Заранее благодарен)

@DartMik commented on GitHub (Apr 1, 2016): О, будь добр, растолкуй мне суть проблемы по этому вопросу и пути её решения на великом и могучем) Заранее благодарен)
Author
Owner

@slr commented on GitHub (Apr 1, 2016):

@DartMik любой произвольно взятый торрент обычно настроен раздаваться некоторым количеством равных частей — например, 100 по 4,0 МБ — и как любой файл в торренте может оказаться в отличном от единицы положительном числе этих частей, так и в любой части может содержаться один и более файлов или фрагментов файлов. библиотека libtorrent, используемая в проекте, качает и раздаёт части полностью, и тем самым, когда ты хочешь скачать только файл А, в части или частях с которым присутствуют файлы или фрагменты файлов Б, В и/или иных, эти файлы также загружаются.
для дальнейшей раздачи их нужно где-то хранить, и qBittorrent, ничтоже сумняшеся, пишет их на диск в соответствии с топологией, определяемой торрентом. в стародавние времена он хранил их в особой директории .unwanted, но затем неким тайным голосованием от неё порешили избавиться.
теоретически, «ненужные» файлы пишутся не абы как, а по уму, место выделяется не под весь файл целиком, только под необходимые данные — что, полагаю, должно определяться отсутствием галочки «Резервировать место на диске для всех файлов» в настройках — но на практике, кажется, не всё так гладко.

рассматриваемое поведение сие, зачастую неочевидное для обычного человека, вызывает часто задаваемый вопрос «доколе?», ответ на который провоцирует дальнейшие, также не лишённые резона, вопросы навроде: «да ну нах?», «неужели это неизлечимо?» и «а как же в других клиентах?». однако по всей видимости лёгких путей к наступлению полного благорастворения воздухов тут нет.

@Meriipu предлагает распространить действие опции «Добавлять расширение .!qB к незавершенным файлам» в том числе на ненужные файлы, а @tp0 предлагает сделать её включённой по умолчанию.
мне лично больше нравится вариант централизованного хранения сопутствующих данных, но не в виде файлов в директории .unwanted, а в виде compressed chunks of the database, т.е. пожатыми и неотсвечивающими.

@slr commented on GitHub (Apr 1, 2016): @DartMik любой произвольно взятый торрент обычно настроен раздаваться некоторым количеством равных частей — например, 100 по 4,0 МБ — и как любой файл в торренте может оказаться в отличном от единицы положительном числе этих частей, так и в любой части может содержаться один и более файлов или фрагментов файлов. библиотека libtorrent, используемая в проекте, качает и раздаёт части полностью, и тем самым, когда ты хочешь скачать только файл А, в части или частях с которым присутствуют файлы или фрагменты файлов Б, В и/или иных, эти файлы также загружаются. для дальнейшей раздачи их нужно где-то хранить, и qBittorrent, ничтоже сумняшеся, пишет их на диск в соответствии с топологией, определяемой торрентом. в стародавние времена он хранил их в особой директории `.unwanted`, но затем [неким тайным голосованием](https://qbforums.shiki.hu/index.php/topic,2294.0.html) от неё порешили избавиться. теоретически, «ненужные» файлы пишутся не абы как, а по уму, место выделяется не под весь файл целиком, только под необходимые данные — что, полагаю, должно определяться отсутствием галочки «Резервировать место на диске для всех файлов» в настройках — но на практике, кажется, не всё так гладко. рассматриваемое поведение сие, зачастую неочевидное для обычного человека, вызывает часто задаваемый вопрос «доколе?», [ответ](https://github.com/qbittorrent/qBittorrent/wiki/Frequently-Asked-Questions#I_configured_qBittorrent_to_not_download_some_files_in_a_torrent_but_they_still_appear_on_my_hard_disk_why_is_that) на который провоцирует дальнейшие, также не лишённые резона, вопросы навроде: «да ну нах?», «неужели это неизлечимо?» и «а как же в других клиентах?». однако по всей видимости лёгких путей к наступлению полного благорастворения воздухов тут нет. @Meriipu [предлагает](https://github.com/qbittorrent/qBittorrent/issues/4918) распространить действие опции «Добавлять расширение .!qB к незавершенным файлам» в том числе на ненужные файлы, а @tp0 [предлагает](https://github.com/qbittorrent/qBittorrent/issues/5023) сделать её включённой по умолчанию. мне лично больше нравится вариант централизованного хранения сопутствующих данных, но не в виде файлов в директории `.unwanted`, а в виде compressed chunks of the database, т.е. пожатыми и неотсвечивающими.
Author
Owner

@DartMik commented on GitHub (Apr 1, 2016):

Спасибо за развернутый ответ! И насколько сложно реализуемо ваше лаконичное решение вопроса? Вы сами участвуете в разработке qBittorrent?

@DartMik commented on GitHub (Apr 1, 2016): Спасибо за развернутый ответ! И насколько сложно реализуемо ваше лаконичное решение вопроса? Вы сами участвуете в разработке qBittorrent?
Author
Owner

@slr commented on GitHub (Apr 1, 2016):

@DartMik да на здоровье. насколько — не знаю. я мимо проходил.

@slr commented on GitHub (Apr 1, 2016): @DartMik да на здоровье. насколько — не знаю. я мимо проходил.
Author
Owner

@native-api commented on GitHub (Apr 3, 2016):

Duplicate of https://github.com/qbittorrent/qBittorrent/issues/4760
See https://qbforums.shiki.hu/index.php/topic,2294.0.html for the root cause.

@native-api commented on GitHub (Apr 3, 2016): Duplicate of https://github.com/qbittorrent/qBittorrent/issues/4760 See https://qbforums.shiki.hu/index.php/topic,2294.0.html for the root cause.
Author
Owner

@kitsame commented on GitHub (May 17, 2016):

I have the same problem.
I was downloading some torrent with 3Gb of pictures arranged inside many folders. I only needed about 15 folders (out of 40). Rest i've put on don't download.
After completing torrent, i've been left with all 40 folders where 15 were complete and rest(unwanted one) had 1-3 pictures per folder. And they were complete pictures, not the files with !qb extension.

Win7 32bit with 3.3.4 version of qbit

@kitsame commented on GitHub (May 17, 2016): I have the same problem. I was downloading some torrent with 3Gb of pictures arranged inside many folders. I only needed about 15 folders (out of 40). Rest i've put on don't download. After completing torrent, i've been left with all 40 folders where 15 were complete and rest(unwanted one) had 1-3 pictures per folder. And they were complete pictures, not the files with !qb extension. Win7 32bit with 3.3.4 version of qbit
Author
Owner

@tp0 commented on GitHub (May 17, 2016):

After completing torrent, i've been left with all 40 folders where 15 were complete and rest(unwanted one) had 1-3 pictures per folder. And they were complete pictures, not the files with !qb extension.

Did you have the files marked as wanted at any point? If you marked the files already in the add new torrent dialog, then I guess not. Since these are apparently fairly small sized pictures it is possible and it downloaded the complete file (to get the required missing piece), and because of that .!qB extension wasn't added?

If you mark some file to be downloaded, download it, and later unmark it, the complete file is moved the .unwanted folder. (Basically I now manually delete the file from file manager and then unmark it from qBit & force recheck the torrent.)

If the part/data file now supported by libtorrent is added to qBit, then these issues should be taken care of.

@tp0 commented on GitHub (May 17, 2016): > After completing torrent, i've been left with all 40 folders where 15 were complete and rest(unwanted one) had 1-3 pictures per folder. And they were complete pictures, not the files with !qb extension. Did you have the files marked as wanted at any point? If you marked the files already in the add new torrent dialog, then I guess not. Since these are apparently fairly small sized pictures it is possible and it downloaded the complete file (to get the required missing piece), and because of that .!qB extension wasn't added? If you mark some file to be downloaded, download it, and later unmark it, the complete file is moved the .unwanted folder. (Basically I now manually delete the file from file manager and then unmark it from qBit & force recheck the torrent.) If the part/data file now supported by libtorrent is added to qBit, then these issues should be taken care of.
Author
Owner

@kitsame commented on GitHub (May 18, 2016):

No, i left them marked as unwanted in add new torrent dialog.

@kitsame commented on GitHub (May 18, 2016): No, i left them marked as unwanted in add new torrent dialog.
Author
Owner

@spumer commented on GitHub (Aug 31, 2016):

I have this bug too, Gentoo x64, v3.3.4 and Windows 7 x64 v3.3.6.
Bug happens only when you start not full torrent, only some files. qBittorrent still download all.
I found a way to workaround this.

  1. Stop the torrent
  2. Remove checkboxes from selected files
  3. Setup checkboxes again
  4. Start the torrent

Now qBittorrent will be download only selected files, not all.

@spumer commented on GitHub (Aug 31, 2016): I have this bug too, Gentoo x64, v3.3.4 and Windows 7 x64 v3.3.6. Bug happens only when you start not full torrent, only some files. qBittorrent still download all. I found a way to workaround this. 1. Stop the torrent 2. Remove checkboxes from selected files 3. Setup checkboxes again 4. Start the torrent Now qBittorrent will be download only selected files, not all.
Author
Owner

@thalieht commented on GitHub (Dec 23, 2017):

Duplicate of #2659

Version 4.0.x is released. It uses libtorrent 1.1.x which puts the unwanted part files in the hidden file
".<torrent_hash>.parts" which is put in the same folder as the root folder(if any) of the torrent.
For the moment it's not possible to put that file somewhere else.

@thalieht commented on GitHub (Dec 23, 2017): Duplicate of #2659 Version 4.0.x is released. It uses libtorrent 1.1.x which puts the unwanted part files in the hidden file ".<torrent_hash>.parts" which is put in the same folder as the root folder(if any) of the torrent. For the moment it's not possible to put that file somewhere else.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#4065
No description provided.