starred/qBittorrent

Fork 0

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

Excluding files #3620

New issue

Closed

opened 2026-02-21 16:52:26 -05:00 by deekerman · 9 comments

deekerman commented

2026-02-21 16:52:26 -05:00

Owner

Originally created by @ghost on GitHub (Dec 23, 2015).

I am on latest version (3.3.1) and files that i exlude when adding a torrent keep downloading anyway.

Originally created by @ghost on GitHub (Dec 23, 2015). I am on latest version (3.3.1) and files that i exlude when adding a torrent keep downloading anyway.

deekerman closed this issue

2026-02-21 16:52:29 -05:00

deekerman commented

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

Author

Owner

@chrishirst commented on GitHub (Dec 23, 2015):

This has been explained many times before.

@chrishirst commented on GitHub (Dec 23, 2015): This has been explained many times before.

deekerman commented

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

Author

Owner

@thalieht commented on GitHub (Dec 24, 2015):

Read #4331 for an explanation.
In the eyes of users this is clearly a bug and these reports will continue if something isn't done about it.

@thalieht commented on GitHub (Dec 24, 2015): Read #4331 for an explanation. In the eyes of users this is clearly a bug and these reports will continue if something isn't done about it.

deekerman commented

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

Author

Owner

@Snurre86 commented on GitHub (Jan 2, 2016):

Just remove the option to edit files/folders and unselect files, problem solved.

@Snurre86 commented on GitHub (Jan 2, 2016): Just remove the option to edit files/folders and unselect files, problem solved.

deekerman commented

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

Author

Owner

@gfairchild commented on GitHub (Jan 6, 2016):

@Snurre86, that is not a solution. Selective downloading is an important standard feature in every major bittorrent client. There is clearly a bug in 3.3.x's implementation of the feature. The correct solution is not to remove the feature but to actually fix the bug.

@gfairchild commented on GitHub (Jan 6, 2016): @Snurre86, that is not a solution. Selective downloading is an important standard feature in every major bittorrent client. There is _clearly_ a bug in 3.3.x's implementation of the feature. The correct solution is not to remove the feature but to actually fix the bug.

deekerman commented

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

Author

Owner

@Snurre86 commented on GitHub (Jan 10, 2016):

Well this feature will never work properly anyway with how BitTorrent is designed see #4385

@Snurre86 commented on GitHub (Jan 10, 2016): Well this feature will never work properly anyway with how BitTorrent is designed see #4385

deekerman commented

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

Author

Owner

@gfairchild commented on GitHub (Jan 10, 2016):

Sure it can. There are certain chunks that are only necessary for excluded files. Those chunks can be ignored. The endpoint chunks for excluded files will need to be downloaded, but that's totally fine. This bug consists of two components:

The chunks exclusive to excluded files should be excluded when downloaded.
The excluded files should be deleted from the hard drive when the torrent is removed from qBittorrent.

@gfairchild commented on GitHub (Jan 10, 2016): Sure it can. There are certain chunks that are _only_ necessary for excluded files. Those chunks can be ignored. The endpoint chunks for excluded files will need to be downloaded, but that's totally fine. This bug consists of two components: 1. The chunks exclusive to excluded files should be excluded when downloaded. 2. The excluded files should be deleted from the hard drive when the torrent is removed from qBittorrent.

deekerman commented

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

Author

Owner

@Snurre86 commented on GitHub (Jan 10, 2016):

I don't think a good solution can be made without changing how BitTorrents work as there are so many bugs here. I have after many years with thousands of torrents just gone back to not edit any file names or exclude any files and I have never had a problem in that field after making that decision. See #4369

@Snurre86 commented on GitHub (Jan 10, 2016): I don't think a good solution can be made without changing how BitTorrents work as there are so many bugs here. I have after many years with thousands of torrents just gone back to not edit any file names or exclude any files and I have never had a problem in that field after making that decision. See #4369

deekerman commented

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

Author

Owner

@gfairchild commented on GitHub (Jan 10, 2016):

The BitTorrent protocol already allows for this situation. Think about it: suppose you have a very large file that has a few KB corrupted somehow. You don't have to redownload the whole file. The client computes the hash of each piece in the torrent, and it only downloads the pieces where the hash doesn't match what the torrent specifies. This functionality is precisely what allows for the ability to exclude files.

Also, every other major torrent client (uTorrent, Deluge, Transmission, etc.) already offers this functionality and has for years. The ability to exclude files is a fundamental feature, and there's absolutely no reason qBittorrent shouldn't make it work the same way.

@gfairchild commented on GitHub (Jan 10, 2016): The BitTorrent protocol already allows for this situation. Think about it: suppose you have a very large file that has a few KB corrupted somehow. You don't have to redownload the whole file. The client computes the hash of each piece in the torrent, and it _only_ downloads the pieces where the hash doesn't match what the torrent specifies. This functionality is _precisely_ what allows for the ability to exclude files. Also, every other major torrent client (uTorrent, Deluge, Transmission, etc.) already offers this functionality and has for _years_. The ability to exclude files is a fundamental feature, and there's absolutely no reason qBittorrent shouldn't make it work the same way.

deekerman commented

2026-02-21 16:52:33 -05:00

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.