I have a three node cluster, the 4.15.17-3-pve kernel is freezing NFS client access on one host (Supermicro X8DT3)
The only difference on this server is a balance-rr setup that directly connects to the NFS server (Fully updated proxmox host.)
Rolling back to the previous 4.15.17-2-pve kernel solves the NFS hanging.
Interestingly enough, when I first boot with the 4.15.17-3-pve kernel I can cd into the mount and browse the NFS share, it's only when booting a VM that freezes the system.
Here's the storage config on the client:
Here's the export on the server:
The only difference on this server is a balance-rr setup that directly connects to the NFS server (Fully updated proxmox host.)
Rolling back to the previous 4.15.17-2-pve kernel solves the NFS hanging.
Interestingly enough, when I first boot with the 4.15.17-3-pve kernel I can cd into the mount and browse the NFS share, it's only when booting a VM that freezes the system.
Here's the storage config on the client:
Code:
nfs: vm
export /rpool/data
path /mnt/pve/vm
server sionis-nfs
content images,rootdir
maxfiles 8
nodes cyrus,lucius
options vers=4.2,async,hard,tcp,noatime
Here's the export on the server:
Code:
/rpool/data 172.16.8.54(rw,async,no_root_squash,no_subtree_check,crossmnt)