Hey all,
I am trying to get ProxMox set up in order to migrate off of Vmware. But I'm running into issues with our NFS mounts.
Currently we have 2 NFS mounts, FreeNAS and NetApp....The FreeNAS mounts just fine. The NetApp mounts, but gives constant hangs and timeouts when trying to access. We are not seeing this on the Vmware side...Any help would be appreciated. The storage is on an isolated 10G network.
Nov 30 12:27:18 ntp-clo1-proxmox-01 kernel: [11883.267099] nfs: server 10.10.0.55 not responding, still trying
Nov 30 12:27:18 ntp-clo1-proxmox-01 kernel: [11883.267101] nfs: server 10.10.0.55 not responding, still trying
Nov 30 12:58:00 ntp-clo1-proxmox-01 kernel: [13725.003257] nfs: RPC call returned error 512
Nov 30 12:58:00 ntp-clo1-proxmox-01 kernel: [13725.003257] nfs: RPC call returned error 512
Nov 30 12:58:00 ntp-clo1-proxmox-01 kernel: [13725.003276] nfs: RPC call returned error 512
Nov 30 14:20:23 ntp-clo1-proxmox-01 kernel: [18668.248337] nfs: server 10.10.0.55 not responding, still trying
Nov 30 14:20:55 ntp-clo1-proxmox-01 kernel: [18700.015082] nfs: server 10.10.0.55 OK
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000
inet 10.10.0.52 netmask 255.255.255.0 broadcast 0.0.0.0
inet6 fe80::eef4:bbff:fed6:acb0 prefixlen 64 scopeid 0x20<link>
ether ec:f4:bb:d6:ac:b0 txqueuelen 1000 (Ethernet)
RX packets 40711809 bytes 59097891957 (55.0 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20307064 bytes 28209187404 (26.2 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@ntp-clo1-proxmox-01:~# nfsstat -rc
Client rpc stats:
calls retrans authrefrsh
717806 100 717808
showmount -e 10.10.0.55
Export list for 10.10.0.55:
/ (everyone)
I am trying to get ProxMox set up in order to migrate off of Vmware. But I'm running into issues with our NFS mounts.
Currently we have 2 NFS mounts, FreeNAS and NetApp....The FreeNAS mounts just fine. The NetApp mounts, but gives constant hangs and timeouts when trying to access. We are not seeing this on the Vmware side...Any help would be appreciated. The storage is on an isolated 10G network.
Nov 30 12:27:18 ntp-clo1-proxmox-01 kernel: [11883.267099] nfs: server 10.10.0.55 not responding, still trying
Nov 30 12:27:18 ntp-clo1-proxmox-01 kernel: [11883.267101] nfs: server 10.10.0.55 not responding, still trying
Nov 30 12:58:00 ntp-clo1-proxmox-01 kernel: [13725.003257] nfs: RPC call returned error 512
Nov 30 12:58:00 ntp-clo1-proxmox-01 kernel: [13725.003257] nfs: RPC call returned error 512
Nov 30 12:58:00 ntp-clo1-proxmox-01 kernel: [13725.003276] nfs: RPC call returned error 512
Nov 30 14:20:23 ntp-clo1-proxmox-01 kernel: [18668.248337] nfs: server 10.10.0.55 not responding, still trying
Nov 30 14:20:55 ntp-clo1-proxmox-01 kernel: [18700.015082] nfs: server 10.10.0.55 OK
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000
inet 10.10.0.52 netmask 255.255.255.0 broadcast 0.0.0.0
inet6 fe80::eef4:bbff:fed6:acb0 prefixlen 64 scopeid 0x20<link>
ether ec:f4:bb:d6:ac:b0 txqueuelen 1000 (Ethernet)
RX packets 40711809 bytes 59097891957 (55.0 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20307064 bytes 28209187404 (26.2 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@ntp-clo1-proxmox-01:~# nfsstat -rc
Client rpc stats:
calls retrans authrefrsh
717806 100 717808
showmount -e 10.10.0.55
Export list for 10.10.0.55:
/ (everyone)