2024-12-16, 10:11 PM
(This post was last modified: 2024-12-16, 10:12 PM by snake. Edited 1 time in total.)
(2024-12-15, 07:10 PM)TheDreadPirate Wrote: I don't see anything in the logs that would explain what is happening. It is direct playing like everything else.
I re-read your original post and are you saying that the jellyfin appdata is on a NFS share? As in the container has to access /config over NFS?
exactly , this is the mount point :
Code:
toto.lan:/mnt/user/appdata/jellyfin on /var/lib/kubelet/pods/187d3e90-fcd9-4355-bd99-9/volumes/kubernetes.io~nfs/appdata-jellyfin-nfs type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.5.99,local_lock=none,addr=192.168.5.98)mapping the appdata in my NAS to the /config into container managed by pv & pvc kubernetes
and looking this page https://jellyfin.org/docs/general/admini...n/storage/ preconize nfsv 4 for the locking file, but if it's nfs editing with a file lock I would have had the problem during my playback test with more than 4 videos simultaneously on the web client + android mobile app.