Torrent Blackhole overwrites files with identical names #1120

New issue

Closed

opened 2026-02-20 10:07:32 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 10:07:32 -05:00

Owner

Originally created by @phoenixtetra on GitHub (Dec 4, 2024).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

When using Torrent Blackhole as the download client, if multiple torrents with the same name are downloaded, the later torrents overwrite the earlier ones. At the end, only the last torrent file remains.

Expected Behavior

If a torrent file with the same name already exists, a number in parentheses is appended to the new file. Ideally, it would be even better to prefix every torrent file with the tracker's name: [Tracker]Title.torrent.

Steps To Reproduce

Bulk download two or more torrents with identical names.

Environment

- OS: Windows 11
- Prowlarr: Prowlarr 1.27.0.4852
- Docker Install: No
- Using Reverse Proxy: No
- Browser: -

What branch are you running?

Master

Trace Logs?

-- Snipped --

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @phoenixtetra on GitHub (Dec 4, 2024). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior When using Torrent Blackhole as the download client, if multiple torrents with the same name are downloaded, the later torrents overwrite the earlier ones. At the end, only the last torrent file remains. ### Expected Behavior If a torrent file with the same name already exists, a number in parentheses is appended to the new file. Ideally, it would be even better to prefix every torrent file with the tracker's name: `[Tracker]Title.torrent`. ### Steps To Reproduce Bulk download two or more torrents with identical names. ### Environment ```markdown - OS: Windows 11 - Prowlarr: Prowlarr 1.27.0.4852 - Docker Install: No - Using Reverse Proxy: No - Browser: - ``` ### What branch are you running? Master ### Trace Logs? -- Snipped -- ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 10:07:32 -05:00

closed this issue
added the
Type: Bug

Area: Download Clients

Status: Maybe One Day

Status: Won't Fix

Status: Unlikely
labels

deekerman commented

2026-02-20 10:07:34 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Dec 4, 2024):

@markus101 upstream nzb and torrent blackhole naming conflict thoughts?

@bakerboy448 commented on GitHub (Dec 4, 2024): @markus101 upstream nzb and torrent blackhole naming conflict thoughts?

deekerman commented

2026-02-20 10:07:34 -05:00

Author

Owner

@markus101 commented on GitHub (Dec 6, 2024):

Don't use blackhole?

Honestly it seems like such an edge case and putting more effort into a "client" that we recommend no one really use doesn't make a lot of sense to me.

If you try to add a duplicate torrent to a client it will fail most of the time as well.

@markus101 commented on GitHub (Dec 6, 2024): Don't use blackhole? Honestly it seems like such an edge case and putting more effort into a "client" that we recommend no one really use doesn't make a lot of sense to me. If you try to add a duplicate torrent to a client it will fail most of the time as well.

deekerman commented

2026-02-20 10:07:34 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Dec 6, 2024):

No plans for this at this time.

Torrent clients would error in the same situation.

@bakerboy448 commented on GitHub (Dec 6, 2024): No plans for this at this time. Torrent clients would error in the same situation.