-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Deluge reports "No such device" #140
Comments
That TZ is not valid |
Also please try the container as a test without the https://github.com/jawilson/deluge-piaportplugin plugin, they may need to make updates to that plugin now that this image has been rebased to Alpine. |
I had similar issues. Likely due to the replatform. I found that rolling back to tag 2.0.5-0202202181752ubuntu20.04.1-ls140 corrected the issue for me. I don't have any plugins configured. I don't think this is a permissions issue, as in my tests, the file was still initialised successfully from the torrent. |
Post your setup. Me and our team cannot replicate this, so there is an outside variable here. |
Yep, I was able to reproduce it with jawilson/deluge-piaportplugin disabled. I'm currently trying to reproduce it with a clean config on macOS, we'll see how that goes. |
All through my mobile, so please excuse any formatting issues. deluge:
image: linuxserver/deluge
container_name: deluge
network_mode: "service:vpn"
depends_on: ['vpn']
environment:
- PUID=995
- PGID=995
- UMASK_SET=000
- UMASK=000
- TZ=${TZ}
volumes:
- ${USERDIR}/deluge:/config
- /media/drv1/VIDEO/Torrents:/downloads
restart: unless-stopped Plugins directory is empty. |
Hmm, I'm also using mergefs. |
I can confirm that the issue is with mergerfs. I created a clean Deluge container (new config), mounted to my boot SSD, and it worked fine. I shutdown the container, changed the mountpoint to my mergerfs mount, and now I'm getting the same "No such device" error. I am able to |
I was able to fix this by removing the Thanks @brott8 for pointing me in the right direction. :) |
I can confirm removing direct_io from mergerfs works |
can you share your whole options ? I replaced direct_io for cache.files=full ? |
Expected Behavior
Torrents shouldn't be stuck with an error message and should download normally.
Current Behavior
All torrents are errrored out with "No such device". Same issue as reported here: #135 (comment)
The exact same config and setup works with version-2.0.5-0202202181752ubuntu20.04.1 but not version-2.0.5-r0 (latest).
It seems like this PR is the source of the trouble: #135
Steps to Reproduce
Not sure what's triggering this so hard to say. Contents of
core.conf
:I'm using a few plugins; PIAPortPlugin is the only one that's not included with Deluge.
Environment
OS: Ubuntu 20.04.3 LTS
CPU architecture: x86_64
Command used to create docker container (run/create/compose/screenshot)
Docker Compose:
Docker logs
The text was updated successfully, but these errors were encountered: