Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certain torrents which contain padding files in them seem to break rTorrent #1156

Open
samad909 opened this issue Mar 2, 2022 · 4 comments

Comments

@samad909
Copy link

samad909 commented Mar 2, 2022

Some torrents with padding files in them (.pad folder) seem to break rtorrent 0.9.8. Trying to start the torrent doesnt work, hash checking or removing the torrent throws this error,
file_list: Failed to prepare file '/.pad/XXXXXX': Duplicate filename found.5) Hashing failed: Duplicate filename found.

There are no duplicate files and the test was done on a new user account.

All the torrents that I have seen this issue on seem to be from private trackers so if you like I can email this torrent to the address on the wiki.

@rakshasa
Copy link
Owner

rakshasa commented Mar 2, 2022

The padding files are themselves duplicates of each other.

@OMEGARAZER
Copy link

This seems to be getting caused by using "V2" or "Hybrid" for the Torrent Format in qBittorrent 4.4.0+. Not sure if that can help diagnose and figure out if there's a way to make it work but that's what I've worked out about it. Seems to come from the newer versions of qB.

@R3yn4ld
Copy link

R3yn4ld commented Jun 9, 2022

I confirm this issue with Hybrid/V2 torrent format on 0.9.6.

Is there any progress on duplicate .pad handling, or any workaround please?

@metaphysicsIO
Copy link

How is this not still handled? I saw this comment:

This is a problem with rTorrent. It does not support hybrid or v2 torrents. You need to use v1 for this software. The torrent must also be created with torrent client that does not optimize alignment. rakshasa/rtorrent#1156

Which is a terrible outlook. "The software other people are using isn't going to work with this, so they need to use v1" -- No, this creates a block in people being able to use rtorrent, because people who use BitComet aren't going to be kind enough to remove this "feature" so rtorrent needs to support ignoring it.

Trust me, no one wants this "feature" supported - We want it ignored so we won't be blocked from using rtorrent to obtain data.

It looks like someone attempted to in 2023 and it has been untouched. How can we make this a reality? What will it take to get this done?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants