Closed paulo-erichsen closed 1 week ago
maybe related to
qbittorrent:4.6.7
Outdated and not supported. Update to the latest version and try to reproduce it again.
Also better use the official docker image to be sure that no 3rd party modifications interfere.
qbittorrent:4.6.7
Outdated and not supported. Update to the latest version and try to reproduce it again.
Also better use the official docker image to be sure that no 3rd party modifications interfere.
I'll upgrade to 5.x once these issues are resolved
after reading the comments from #16080 I found out that using libtorrentv1
is a workaround. I've been using linuxserver/qbittorrent:4.6.7-libtorrentv1
for a few days now and haven't had another issue with qbittorrent downloading directly to an NFS share.
Closing this issue as it's a duplicate of #16080 and the workaround has been working
qBittorrent & operating system versions
Host PC OS: Arch Linux - Linux 6.11.6-arch1-1 qbittorrent: linuxserver/qbittorrent:4.6.7 (docker)
NAS Server OS: TrueNAS-13.0-U5.3 (Core) has NFS shares for downloads and media
What is the problem?
I'm running into some issues with qbittorrent lately. qbittorrent runs on docker, but the SavePath and TempPath are located in an NFS mount point. After so many hours downloading lots of data, the kernel starts throwing exceptions / stack traces and qbit stops responding. Running docker stop qbittorrent won't work because it fails to stop the container. The only way to get it going again is to do a full reboot of the PC running qbittorrent.
Steps to reproduce
No response
Additional context
No response
Log(s) & preferences file(s)
qBittorrent.conf
journal logs
$ mount | grep download