lp0101

I ended up solving this finally. The solution was the turn of SMB on the affected shares. It looks like having both SMB and NFS for some reason lead to the errors.

Unfortunately I use hardlinks pretty extensively, so 1 isn't an option. 2 isn't great either, I do frequent 1+gb/s transfers on this share I don't think it's 3 - I have the same issue across multiple machines with multiple linux OS's. Right now, all 3 are Ubuntu 22.04 machines, but still. Diagnostics attached. barad-dur-diagnostics-20231022-1710.zip

Output of `mount -v`: Looks like it's NFSv4 I've tried as well without setting the flag, same behaviour - this was when mounting with fstab instead of autofs. For completion's sake, this is the autofs config I'm using to mount it:

I've been trying to get NFS to play nice with unRAID for a while, and I'm really not sure where to go from here. All the shares I'm sharing are user shares with `Cache: Yes`. I'm sharing the shares from my unRAID box to 3 Kubernetes nodes, mounted with autoFS. This is a sample output of nfsstat to show it's using the correct version: /mnt/autofs/media from 192.168.10.120:/mnt/user/media Flags: rw,relatime,vers=4.2,rsize=8192,wsize=8192,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.10.171,local_lock=none,addr=192.168.10.120 I've also set my `fuse_remember` tunable to -1, which in theory should solve the stale file handle issues, but it doesn't. If I ever add files to this share, once the mover runs, I'm going to experience the stale file handle error on my nodes. Applications (containers) continue to work, but if they're restarted, they'll fail to start with the stale file mount error. As usual, the fix is to unmount and remount, which involves stopping all the applications that are using the share. Is there any advice on possible other fixes? Anything flags I should add to the mount?

I'm having some weird issues with speed. I have a gigabit connection. When starting a large torrent, the speed will shoot up to ~80-100 MBps no problem, stay there for a few seconds, and then plummet back down to the single digits, sometimes as low as 2 MBps. It'll stay there for the rest of the download, not speeding up. This even happens with slower torrents. A bad torrent might start at around 15 MB/s, then also drop down after a few percent has finished to the single digits. I'm using wireguard with mullvad. I can confirm the server I'm connecting to is capable of gigabit speeds, so I'm not really sure what the issue is. Connections status is green, so the port is properly forwarded. I also set the protocol to TCP only, but no luck with either TCP or TCP/uTP Edit: Just bought a month of PIA, same issue. The speed will shoot up, then drop significantly. Edit2: Just tested a torrent on my desktop using the same wireguard config. It's not as aggressive, but it still dropped from 80 MB/s to ~20 MB/s. So I guess it isn't an unraid-specific issue. Maybe something to do with my ISP? Weird that VPN traffic would be throttled though