Replies: 4 comments 8 replies
-
|
There were some instances where this might happen when switching back to 2.94 from 3.0 transmission client.. need to stop, clean the torrent folder then restart |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your response. When you say "clean the torrent folder," do you mean delete out all of the torrent files in there? Or would it be something more selective? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, delete the torrents and resume files.. as the two versions use
different hashing algorithms
…On Fri, 16 Sep 2022 at 21:59, DrR0Ck ***@***.***> wrote:
Thanks for your response. When you say "clean the torrent folder," do you
mean delete out all of the torrent files in there? Or would it be something
more selective?
—
Reply to this email directly, view it on GitHub
<#2343 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7OFYQZMLVQOGNADU46DZTV6RVL7ANCNFSM6AAAAAAQKR3RIA>
.
You are receiving this because you commented.Message ID:
<haugene/docker-transmission-openvpn/repo-discussions/2343/comments/3662486
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I stopped the container, deleted the torrents and resumes, and when I restarted the container, I had no torrents. I then stopped everything and moved the torrents back in, and restarted, and all the torrents were there, but I had lost all my stats and dates. So I put the resumes back in and everything was back. Was I supposed to delete the torrents/resumes while the container was running? I assumed that if I was deleting the files that there was some master database that had the information, but I gather that is not the case - at least not across sessions. |
Beta Was this translation helpful? Give feedback.
-
|
As you moved back transmission versions your best move is to get rid of all resumes and move the torrents out, then only re-add the ones you want to continue seeding and let transmission re-verify. |
Beta Was this translation helpful? Give feedback.
-
|
Got it. Understood. Will give it a go. |
Beta Was this translation helpful? Give feedback.
-
|
Is there any way to do this and not be starting from scratch as far as torrent dates, totals uploaded, etc.? |
Beta Was this translation helpful? Give feedback.
-
|
Or any way to export out this info and overlay it back in? |
Beta Was this translation helpful? Give feedback.
-
|
Which info? Client stats are saved in stats.json file in transmission-home,
this isn’t affected by deleting the .resume and .torrent files.
…On Sun, 18 Sep 2022 at 10:04, DrR0Ck ***@***.***> wrote:
Or any way to export out this info and overlay it back in?
—
Reply to this email directly, view it on GitHub
<#2343 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7OFYTSIM64QSHNBGEJMS3V6ZTBVANCNFSM6AAAAAAQKR3RIA>
.
You are receiving this because you commented.Message ID:
<haugene/docker-transmission-openvpn/repo-discussions/2343/comments/3672316
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
The per-torrent stats. Each torrent has date added info and the uploaded ever (total) column. these would be the ones I would most want to keep. I was able to clean out all of the .torrent and .resume files for old stuff I am no longer seeding, and then I did re-checks on everything still seeding. I guess this isn't going to get the job done, is it? |
Beta Was this translation helpful? Give feedback.
-
|
Can I ask what you need that date for? Seems pointless to me.. but no,
that’s not going to work. Either you upgrade to 3.0 client (either switch
back to 3.7.1 or upgrade transmission on a startup script, check discussion
thread) or you remove all torrents and only re-add those you want to keep
and restart
…On Sun, 18 Sep 2022 at 11:40, DrR0Ck ***@***.***> wrote:
The per-torrent stats. Each torrent has date added info and the uploaded
ever (total) column. these would be the ones I would most want to keep. I
was able to clean out all of the .torrent and .resume files for old stuff I
am no longer seeding, and then I did re-checks on everything still seeding.
I guess this isn't going to get the job done, is it?
—
Reply to this email directly, view it on GitHub
<#2343 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7OFYR5UMAKIU5B3MO4BG3V6Z6IPANCNFSM6AAAAAAQKR3RIA>
.
You are receiving this because you commented.Message ID:
<haugene/docker-transmission-openvpn/repo-discussions/2343/comments/3672528
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I have a finite amount of storage to devote to torrents. I use the dates combined with the upload totals to periodically decide which torrents to keep and which to delete to make room for new ones. Regardless, I appreciate the help. This is not a life and death type problem. I'll delete everything and re-add the torrents I want to keep if that ensures it will make things work. I prefer not to roll back to an older version and forego updates, and I prefer not to upgrade my instance to a Transmission version different from the one in the container releases as I will then have to upgrade every time a new version rolls out. |
Beta Was this translation helpful? Give feedback.
-
I am finding that when I attempt to clean up multiple torrents via deleting from the front end, that the deleted torrents reappear after a restart of the container. This is problematic as I do not want the torrents downloaded again, and I then have to hunt down the .torrent files based on the hash value, which is kind of a pain. So I am wondering whether this is a bug or if I might have something misconfigured. Any assistance would be appreciated. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions