[SOLVED] hostname kernel: [887657.076734] nfs: server 192.168.yyy.xxx not responding, timed out

[jlmorgado]

Hi,

I've noticed I'm getting the below messages in all nodes of my cluster.

Feb 6 01:44:38 hostname kernel: [887657.076734] nfs: server 192.168.yyy.xxx not responding, timed out

I've tried (and succeeded) adding a NFS Storage with the same IP address, but a bit after, deleted it using the Web UI.

Is there something I need to do to manually remove any mount or something?

Thanks in advance,
J.

 

[jlmorgado]

Hi,

I've tried unmounting the NFS share I had used previously to host some templates (which I later discovered I can't use for that purpose) but I'm still getting the same error in the logs.

Any idea on how to solve this?

Thanks in advance,
J.

 

[jlmorgado]

OK, got it.

umount -f /path/to/mount

Then restarted all Proxmox nodes, one by one, after moving VM's around to active nodes.

J.

 

[Roberto17]

I have the same problem. After removing NFS storage started seeing syslog entries with "kernel: nfs: server X.X.X.X not responding, timed out". Rebooting the node solves the problem in that node, as jlmorgado said, but it seems to me an overkill. I have too many nodes, moving all vms around to reboot all nodes will be impractical. Isn't there any other way?

 

[virtx]

@Roberto17

Maybe you can try to use `soft` option for mounting NFS resources. https://serverfault.com/questions/9...advantages-of-hard-versus-soft-mounts-in-unix

Or `hard,intr` https://unix.stackexchange.com/ques...fs-connection-from-freezing-the-client-system