MarcMo

it was resolved by using nfsv4 and disabling hard link in unraid

Hello everyone, I'm experiencing persistent issues with NFS mounts between my Proxmox server and Unraid server, specifically involving LXC containers. I'm hoping to get some insights or suggestions from the community to resolve this problem. Issue Description: Symptom: The NFS mounts on the Proxmox server hang, causing commands like ls /mnt/data to become unresponsive. Observation on Unraid Server: nfsd processes are stuck in the D (uninterruptible sleep) state. Restarting NFS services on Unraid doesn't resolve the issue. Attempts to Unmount NFS Shares: Running umount -f /mnt/data on Proxmox results in "device is busy" errors. Network Connectivity: Both servers can ping each other. No apparent network issues like packet loss or high latency. Additional Notes: Other services on both servers appear to function normally. Network Configuration: Proxmox Server (pve): IP Address: 10.0.0.2 Role: Hosts several LXC containers and mounts NFS shares from the Unraid server. Unraid Server (Tower): IP Address: 10.0.0.3 Role: Provides NFS shares to the Proxmox server. Network Details: Subnet: 10.0.0.0/12 Gateway: 10.0.0.1 DNS Servers: 10.0.0.1 (FYI: my router had some dns issues last week) Both servers have static IP addresses assigned. LXC Container Configuration: I have an LXC container running on the Proxmox server configured as follows: Container ID: 105 Hostname: qbittorrent Purpose: Runs a torrent client that downloads directly to an NFS-mounted share. Network: Type: Virtual bridge (vmbr0) IP Address: Assigned via DHCP within the same subnet (10.0.0.x). Mounts: NFS share from Unraid mounted directly inside the container at /mnt/data. My host (proxmox) fstab: and my LXC config Debug Findings: On Unraid Server (Tower): NFS Daemon Processes: RPC Services: System Logs: No significant errors related to disks, network, or NFS found in /var/log/syslog or dmesg. nfsd processes remain in the D state even after restarting NFS services. On Proxmox Server (pve): Attempted unmount: Kernel messages Questions and assistance needed: Could the nfsd processes being stuck in the D state be caused by the LXC container accessing the NFS share directly? The container runs a torrent client that downloads directly to the NFS-mounted share while keeping all AppData on Proxmox for easier backups. Could network misconfigurations cause this issue, even though both servers have static IPs and can ping each other? What did I set up wrong? What I've tried so far: Restarted NFS services on both servers. Attempted to unmount NFS shares using umount -f, but received "device is busy" errors. Checked for disk errors and system logs on Unraid; found no significant issues. Verified network connectivity and configurations; no apparent issues found. Additional Information: System Versions: Unraid OS: Version 6.12.3 Proxmox VE: Version 7.4-3 NFS Version Used: NFSv4.2 Export options on Unraid: Mount Options on Proxmox: Any help or suggestions would be greatly appreciated! I'm open to any troubleshooting steps or best practices that could help resolve this issue. If more information is needed, please let me know, and I'll provide it. I've been fighting with it for over a week now and nothing besides hard reset helps.