Page 1 of 1

Downloads folder gets deleted after completed download gets moved

Posted: Tue Mar 10, 2020 8:39 am
by kevindd992002
I have the the linuxserver\deluge container setup so that it moves completed downloads to a different folder. However, every single time a download completes it does move it successfully to the destination folder but also deletes the downloads folder (/downloads/torrent) itself. This results to an "error" message in the lower right hand side of the webGUI because it cannot compute the available space. Is this normal?

Re: Downloads folder gets deleted after completed download gets moved

Posted: Tue Mar 10, 2020 1:17 pm
by shamael
Hi, and no. May you please share the options used in preferences>downloads?
I don't move the completed torrent, they all remains in the download folder however it may be a path issue.

Have you tried with a recent Deluge/libtorrent version?

Re: Downloads folder gets deleted after completed download gets moved

Posted: Tue Mar 10, 2020 1:50 pm
by kevindd992002
Sure. Here you go:

Image

And here are my volumes in my docker compose file:

volumes:
- /home/kevin/appdata/deluge:/config
- /home/kevin/downloads:/downloads
- /mnt/storage/downloads_complete:/storage/downloads_complete

"/home/kevin/downloads" is in a different volume compared to that of the "/mnt/storage/downloads_complete" but still that shouldn't affect any deletion of the downloads folder. I have not tried with the Deluge\libtorrent version yet.

Re: Downloads folder gets deleted after completed download gets moved

Posted: Tue Mar 10, 2020 1:51 pm
by kevindd992002
Any logs I can provide for us to be able to come to the bottom of this?

Re: Downloads folder gets deleted after completed download gets moved

Posted: Thu Mar 12, 2020 4:02 pm
by Shryp
This thread sounds similar to your issue and includes a work around by adding a dummy file to the download folder: viewtopic.php?p=231325#p228853

Re: Downloads folder gets deleted after completed download gets moved

Posted: Thu Mar 12, 2020 4:23 pm
by kevindd992002
Thanks for that. I will try the workaround. This should've been fixed a long time ago.