Deluge not remembering some torrents that were added (any torrents with 0 Bytes)
Posted: Fri Apr 02, 2021 2:25 am
When I start Deluge, I notice that some torrents are lost from the previous session.
Taking screenshots to compare, it looks like torrents that were added and showed
on list but the size column shows at 0 Bytes at time of shutdown were removed
from next startup (no longer showing). As soon as they eventually show their actual
file size (may take minutes or indefinitely), they won't be lost.
Is this to be expected? I add all my torrents via magnet links instead of
.torrent files because all my torrents tend to have magnet links but only some
have .torrent files. As a result, it's problematic for me because torrents that
were 0 Bytes when Deluge quits will be lost unless I manually save and keep
track of magnet links that were added to Deluge. Would a .torrent file ensure
torrents will never be lost since Deluge could always reference it? Could a .torrent
file be generated from a magnet link if the torrent site does not provide one?
Since the size column shows 0 Bytes as opposed to the actual size of the files
to be loaded by the torrent, I assume that means Deluge hasn't even downloaded
the metadata for the torrents which might be needed to reference on next startup
in order to continue the download. Shouldn't this happen as soon as I add the
magnet link? Is the only way to avoid this to make sure Deluge shows the actual
size of the files and save the magnet links to a text file for any that shows as
0 Bytes so I can add them the next time I start up Deluge?
Is it possible to retrieve a list of all torrents (e.g. magnet links) from the
list of the current session and/or prior session in order to back this up to
prevent the possibility of losing torrents that were added in my situation? I'm
looking at ~/.config/state/ but it doesn't seem clear for finding magnet links
or torrent names. EDIT: Actually, it looks like torrents.state does show it but it's a
binary file. How can I extract all magnet links and torrent name nicely?
Any suggestions or alternatives to my workflow is much appreciated. I'm on Arch
Linux on the latest version of deluge (2.0.4).
EDIT: Just tried AutoAdd and it does not solve this problem. I added a text file with
a magnet link, then it gets automatically added to the torrent list. While it shows 0 B,
I close Deluge and start it back up to see if the torrent is "lost". It is, and the
example.magnet in the watch folder renames to example.magnet.invalid (as opposed
to example.magnet.added, due to this viewtopic.php?t=55694).
However, the alarming thing is that if I add a example2.magnet with the same magnet
link inside, it will rename to example2.magnet.invalid but not add the torrent.
If I restart Deluge again, then it will add the torrent if I rename example2.magnet.invalid
to example2.magnet. So this implies torrents that were added to Deluge but has a size
of 0 Bytes when Deluge is closed resulting in them being lost on next restart can still somehow
be referenced by Deluge on the restart despite not being in the torrent list. Only on another
restart will the reference be cleared and the user allow to re-add the torrent for it to
show up. Adding a torrent that shows 0 B and then removing it in the same session does
not have the same problem--I can re-add the torrent in that same session successfully,
so the problem is specific to torrents that shows as 0 B before Deluge is shutdown.
Taking screenshots to compare, it looks like torrents that were added and showed
on list but the size column shows at 0 Bytes at time of shutdown were removed
from next startup (no longer showing). As soon as they eventually show their actual
file size (may take minutes or indefinitely), they won't be lost.
Is this to be expected? I add all my torrents via magnet links instead of
.torrent files because all my torrents tend to have magnet links but only some
have .torrent files. As a result, it's problematic for me because torrents that
were 0 Bytes when Deluge quits will be lost unless I manually save and keep
track of magnet links that were added to Deluge. Would a .torrent file ensure
torrents will never be lost since Deluge could always reference it? Could a .torrent
file be generated from a magnet link if the torrent site does not provide one?
Since the size column shows 0 Bytes as opposed to the actual size of the files
to be loaded by the torrent, I assume that means Deluge hasn't even downloaded
the metadata for the torrents which might be needed to reference on next startup
in order to continue the download. Shouldn't this happen as soon as I add the
magnet link? Is the only way to avoid this to make sure Deluge shows the actual
size of the files and save the magnet links to a text file for any that shows as
0 Bytes so I can add them the next time I start up Deluge?
Is it possible to retrieve a list of all torrents (e.g. magnet links) from the
list of the current session and/or prior session in order to back this up to
prevent the possibility of losing torrents that were added in my situation? I'm
looking at ~/.config/state/ but it doesn't seem clear for finding magnet links
or torrent names. EDIT: Actually, it looks like torrents.state does show it but it's a
binary file. How can I extract all magnet links and torrent name nicely?
Any suggestions or alternatives to my workflow is much appreciated. I'm on Arch
Linux on the latest version of deluge (2.0.4).
EDIT: Just tried AutoAdd and it does not solve this problem. I added a text file with
a magnet link, then it gets automatically added to the torrent list. While it shows 0 B,
I close Deluge and start it back up to see if the torrent is "lost". It is, and the
example.magnet in the watch folder renames to example.magnet.invalid (as opposed
to example.magnet.added, due to this viewtopic.php?t=55694).
However, the alarming thing is that if I add a example2.magnet with the same magnet
link inside, it will rename to example2.magnet.invalid but not add the torrent.
If I restart Deluge again, then it will add the torrent if I rename example2.magnet.invalid
to example2.magnet. So this implies torrents that were added to Deluge but has a size
of 0 Bytes when Deluge is closed resulting in them being lost on next restart can still somehow
be referenced by Deluge on the restart despite not being in the torrent list. Only on another
restart will the reference be cleared and the user allow to re-add the torrent for it to
show up. Adding a torrent that shows 0 B and then removing it in the same session does
not have the same problem--I can re-add the torrent in that same session successfully,
so the problem is specific to torrents that shows as 0 B before Deluge is shutdown.