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

Can't delete 3 particular torrents whatewer i do. #4702

Closed
TiberiumFriend opened this issue Jan 28, 2016 · 32 comments
Closed

Can't delete 3 particular torrents whatewer i do. #4702

TiberiumFriend opened this issue Jan 28, 2016 · 32 comments

Comments

@TiberiumFriend
Copy link

They just came back again and again, other torrents seem to delete fine.
I tried to start qBittorent as Administrator. tried to let them download and only then delete them tried to delete them one by one.
uzbpbmw

System - Windows 10, 64, qBittorent version 3.3.3 it started happening around 2 updates ago.

@sledgehammer999
Copy link
Member

  1. Delete them
  2. Open log: View -> Log
  3. Select all, right click, copy
  4. Paste here.

@TiberiumFriend
Copy link
Author

log deleted by sledgehammer999

@sledgehammer999
Copy link
Member

It doesn't show an error but do these:

  1. While running qbt, select each of the 3 torrents and note down their infohash (General button at the bottom of the window)
  2. Close qbt
  3. Go to C:\Users\<username>\AppData\Local\qBittorrent\BT_backup
  4. Locate the files that have this naming scheme <infohash.torrent> and <infohash.fastresume.<number> and match the infohashes you noted from step 1. You should locate 6 files in total.
  5. Right click on each one of them and select "properties". Can you post their properties here? (eg read-only)
  6. Then delete those 6 files.
  7. Start qbt. Now the torrents shouldn't reappear.

29.01.2016 1:52 - Unable to resume torrent 'ce7f4d86600b8d5ef5f3b220746b330176b13bb9'.
29.01.2016 1:52 - Unable to resume torrent 'cba2693fbc13b0e1f3fb7b4cc972c83caddf0f0f'.
29.01.2016 1:52 - Unable to resume torrent 'b73128a87c870d88f0232d082cd092d88aaf9bd8'.
29.01.2016 1:52 - Unable to resume torrent 'ae0f42ed1878f27ab434933b37eafaaed3bb40e6'.
29.01.2016 1:52 - Unable to resume torrent 'a85bf298a092b258dadae876dbaf842686732fb0'.
29.01.2016 1:52 - Unable to resume torrent '8326dd17467cd171b156328c052259be4daf03cc'.

I think you should delete these too from the BT_backup folder. These are leftover files from older versions that cannot be resumed.

@TiberiumFriend
Copy link
Author

Thanks, ill do this later today.
Can i delete previous post with log? Don't want it to lie around.

@sledgehammer999
Copy link
Member

I just edited it.

@ghost
Copy link

ghost commented Jan 29, 2016

I was also having this issue as well.

@Musickiller
Copy link

+1. Same trouble.

@sledgehammer999
Copy link
Member

Well you can try what I said above and post your findings.

@Musickiller
Copy link

wait. it is strange. they were there for a long time. one particular caused me trouble for several months. and now (just now) there are gone! X_X

Thanks The Machine Spirit for your grace and good will!

EDIT 23:47
Now it's bugging me... What on Earth happened just now?! How?! -_-

EDIT 23:56
You know, what's funny? everything began to work as soon as I sent 0.2 LTC as a donation xD Not much but it worked!

@sledgehammer999
Copy link
Member

work as soon as I sent 0.2 LTC as a donation xD Not much but it worked!

I think qbt has become self-aware. I must kill it with fire. [/offtopic]

@TiberiumFriend
Copy link
Author

  1. Right click on each one of them and select "properties". Can you post their properties here? (eg read-only)

http://a.pomf.cat/vnfcen.png
And there is only 3 fast resume file, no torrent files.

Aaand it didn't helped.
They magically coming back again and again.
Here my qBittorent folder from AppData Local, backup.rar is the same before i started deleting anything.

https://mega.nz/#!hlAwAZ4K!DYb19TXCm8xoMqIwsMMbtyvzKRWRk_-YZQRL_MJlqDg

@sledgehammer999
Copy link
Member

Well russian screenshots don't help.

But anyway, I found out why they reappear which is very very weird. There 3 files in the BT_backup folder that their actual infohash is different that the one in their name. I cannot understand how that happened. qBittorrent creates files in that folder using the infohash reported by libtorrent and that infohash doesn't change for the same torrent.
If you delete the files having these infohashes you'll be fine:

2f64ffa675a3e19dd5f1daa0d1845c26c5cfe4d6
7e63d7654322689a9ae5275f4c55624589fa81a3
9485ec519febafa2782bf20228bc14b145cdf80e
bef9ae91d41e119c8977478279522a64095bc5db
e456b083a30f738c40d45f6970df27266d5cb6c3
9ec7444bf57c79bd92787b25a2c6c79504d8fbe8

@glassez I am bringing this to your attention just so you know. I doubt you know what caused this. The first 3 hashes are the hashes in the filenames. The next 3 hashes are the hashes shown by qbittorrent when I loaded the files.

for anyone having similar problems

  1. Close qbt
  2. Go to your BT_backup folder
  3. Backup it and then delete it
  4. Launch qbt
  5. From the backup drag-n-drop the .torrent files one by one.
  6. Check the infohash that is printed in the "Add New Torrent" dialog. (at the bottom).
  7. If it matches the one in the filename proceed to the next .torrent file but first click Cancel on the dialog. You don't want to add it to the session.
  8. If it doesn't, delete that file along with its fastresume. Also delete the files that have the real hash in their names. Don't forget to click Cancel on the dialog. You don't want to add it to the session.
  9. After you're done, close qbt, copy the BT_backup folder back to its place and relaunch qbt.

@TiberiumFriend
Copy link
Author

It helped!
Thanks sledgehammer999.

@Musickiller
Copy link

Well, I'm back with a bug of a bug. Remember I said torrents disappeared? It was a bug of a bug. They are back now. In Backup folder there was only 1 file for each 1 of not working torrent (no .torrent file). Removing files with 1'st method did not work (reappeared). So I'm gonna do a cleanup and report stuff here afterwards.

EDIT 14:50
It's funny to begin a day with backing up a backup folder with bugs. ^_^

EDIT 15:01
Well.. It was no fun to do that with my 68 torrents =(
But I've spotted problematic torrents (with wrong hash), plus delelted one unrequired resume file.
Everything fine now. Thanks man.
I always loved sledgehammers! They solve so many problems!

@glassez
Copy link
Member

glassez commented Feb 1, 2016

infohash doesn't change for the same torrent

Really it may be changed in some VERY specific cases. For some reason we do not process this situation. We ought to fix it.

@sledgehammer999
Copy link
Member

Really it may be changed in some VERY specific cases. For some reason we do not process this situation. We ought to fix it.

Do you know which cases? Can you enlighten me?

@glassez
Copy link
Member

glassez commented Feb 1, 2016

Do you know which cases? Can you enlighten me?

See http://www.rasterbar.com/products/libtorrent/reference-Alerts.html#torrent_update_alert. However, the example given there, does not fit us. But, there should probably be other cases.

@sledgehammer999
Copy link
Member

@arvidn I hate to tag you again, but can you enlighten us? Assume RC_1_0. Is there a case where the initially reported hash changes after a while? If yes, can you tell us when? (apart from the above linked doc).

@arvidn
Copy link
Contributor

arvidn commented Feb 1, 2016

yes! When a torrent is added by URL, the info-hash is not known initially. Once downloaded, the info-hash will change. The event of changing info-hash will be notified via an alert.

@arvidn
Copy link
Contributor

arvidn commented Feb 1, 2016

I'm starting to think it was a mistake to add this feature to libtorrent btw...

@glassez
Copy link
Member

glassez commented Feb 2, 2016

yes! When a torrent is added by URL

@arvidn, this is the only case? The fact is that we do not add torrents by URL, and we download torrent files ourselves.
I guess we will have to search for the hidden source of the problem.

@glassez
Copy link
Member

glassez commented Feb 2, 2016

@TiberiumFriend, can you provide links to the web pages from where you got this torrents? Did you add it via magnet links or via torrent files?

@arvidn
Copy link
Contributor

arvidn commented Feb 2, 2016

I can't see any other way for it to happen in libtorrent

@TiberiumFriend
Copy link
Author

@glassez
Here http://www.ex.ua/91988360
Here, you might have some trouble with access to this though.

@Musickiller
Copy link

@glassez For me - it was a magnet from btdigg.org and a magnet from thepiratebay.org. I don't use torrents usually.

@glassez
Copy link
Member

glassez commented Feb 2, 2016

Here, you might have some trouble with access to this though.

@TiberiumFriend
Ok. Then could you give me the original torrent files from this site?

@TiberiumFriend
Copy link
Author

@glassez
Here you go.
torrents.zip

@yevgeniy-1
Copy link

I also having this issue, can't delete 3 particular torrents:

@sledgehammer999
Copy link
Member

I also having this issue, can't delete 3 particular torrents:

@yevgeniy-1 try following my instructions under the title for anyone having similar problems in my #4702 (comment)

@yevgeniy-1
Copy link

@sledgehammer999
I found an easier way.
Go to C:\Users\ username \AppData\Local\qBittorrent\BT_backup
Just use the search text, inside torrent files, using the torrent name, and delete them.
I used "FAR manager" for it.

@xak2000
Copy link

xak2000 commented Sep 14, 2016

@yevgeniy-1's approach worked for me too. I used Total Commander but any software that can search files in particular folder by content will suffice.

Thanks!

@ngosang
Copy link
Member

ngosang commented Sep 16, 2018

We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.

@ngosang ngosang closed this as completed Sep 16, 2018
@qbittorrent qbittorrent locked and limited conversation to collaborators Feb 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants